Hmmm... okay. Maybe I should have been more descriptive considering your earlier statement "I'm not massively familiar with the intricacies of XML or the facilities available in .NET to process it". ;-)
Well, you can bring about a transformation using C# code. There is no requirement to include a stylesheet element within the XML itself. Since this happens silently in code, the user never comes to know how the XML has been transformed. When I say "parameter", I mean XSL parameter. Again this is passed to the XSLCompiledTransform object via the XsltArgumentList parameter. On Jan 25, 5:36 am, Knickerless Parsons <[email protected]> wrote: > Thanks for the response, > As long as the solution is as simple to use from the users view, I > don't mind how it's implemented. When you say a parameter, are we > talking command line stuff or could we use an application like MS XML > Notepad? There's an XSLT tab I noticed but to get anything out of it I > needed to add a reference to the stylesheet into the source document > which the users aren't going to be happy with. > > The other things I should have mentioned were: > > * I'm rolling this out to locked down desktops so the scope for > installing new applications is going to be restricted > * I don't know if the result file is processed using XML aware code or > just plain old file processing so I don't want any additional tags > appending to the header of the document. > > Ta, > Dave. > > On Jan 24, 11:49 am, Cerebrus <[email protected]> wrote: > > > > > What you are trying to achieve is in effect nothing more than a > > transformation of a master XML into a filtered version. For this > > purpose, an XSLT would be the best method, IMHO. The XSLT will accept > > the filter criterion as parameter and return a filtered output.- Hide > > quoted text - > > - Show quoted text -
