EDN Admin
Well-known member
Now that Ive taken a few strolls in the .Net XML environment...
Goal: Create a web based admin utility to control sending orders via a web service.
Requirements: Either by holding the settings in SQL or XML enable the utility to be configurable to add, remove, change any of the resulting XML; including name spaces, data name/value pairs, formatting, all without having to rebuild the c# component.
My Plan (flawed as it may be): For the utility programs settings, use XML rather than my more familiar SQL. In no particular order, although numbered...
1. XML template that contains all of our static data to send an order, like our company name & address info, and elements as placeholder datafields to replace with current order data.
2. XML Data relation of name/value pairs of SQL database query column names and their corresponding XML order element names.
3. *New* XSLT to fix up a few items, make pretty, like add the small boat-load of xmlnss that needed to be included in the root <TXLife> element; I know that I could do this with LINQ, but in order to be better aquainted with XML/XSLT and ensure that
the utility is truely dynamic, Im thinking that this should be achieved using an XSLT doc.
4. Web Application so it can be accessed anywhere within the LAN/VPN.
<hr class="sig JeffP...
View the full article
Goal: Create a web based admin utility to control sending orders via a web service.
Requirements: Either by holding the settings in SQL or XML enable the utility to be configurable to add, remove, change any of the resulting XML; including name spaces, data name/value pairs, formatting, all without having to rebuild the c# component.
My Plan (flawed as it may be): For the utility programs settings, use XML rather than my more familiar SQL. In no particular order, although numbered...
1. XML template that contains all of our static data to send an order, like our company name & address info, and elements as placeholder datafields to replace with current order data.
2. XML Data relation of name/value pairs of SQL database query column names and their corresponding XML order element names.
3. *New* XSLT to fix up a few items, make pretty, like add the small boat-load of xmlnss that needed to be included in the root <TXLife> element; I know that I could do this with LINQ, but in order to be better aquainted with XML/XSLT and ensure that
the utility is truely dynamic, Im thinking that this should be achieved using an XSLT doc.
4. Web Application so it can be accessed anywhere within the LAN/VPN.
<hr class="sig JeffP...
View the full article