Yes, there have been discussions on the public newsgroups regarding XslTransform's performance. It seems that performance was not fully addressed in order to meet deadlines. You should see comparable results to MSXML when transforming using an XPathDocument as the source (because it is forward-only, non-caching). There have also been suggestions to use interop with MSXML 4.0 if performance is questionable until .NExT.
The discussions should be available through searching archives for microsoft.public.xml and microsoft.public.xsl. Kirk Allen Evans http://www.xmlandasp.net "XML and ASP.NET", New Riders Publishing http://www.amazon.com/exec/obidos/ASIN/073571200X > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED]]On Behalf Of Axel Heitland > Sent: Wednesday, July 10, 2002 5:18 PM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] Slow XSLT.transform > > > Hi all, > > are there any known performance issues with the XslTransform class?! > We've done some measurements with the MSXML-COM-Implementation and > XslTransform and got some very disappointing results - both got the > input and produced the same output, but the COM-based program took 0.3 > sec whereas the XslTransform took 30 sec - that what I call a difference > ;-) > > Any pointers? > > Axel > > You can read messages from the Advanced DOTNET archive, > unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
