Altova Mailing List Archives>Archive Index >microsoft.public.xsl Archive Home >Recent entries >Thread Prev - Re: Making XSLT Transform faster [Thread Next] Re: Making XSLT Transform fasterTo: NULL Date: 4/10/2009 9:14:00 AM You can just give them the new assembly provided it has same name and type etc. or it's configurable. One problem we found was that you can't sign the assembly which can lead to problems. -- Joe Fawcett (MVP - XML) http://joe.fawcett.name "Zest4Quest" <Zest4Quest@d...> wrote in message news:71CD6F44-56D7-4995-8F52-D9EF869AFACD@m...... > Hi Martin, > If i compile the xslt and use an assembly, when i make any changes to the > xslt in future, does that mean i will have to re-deply the application > using > it(new assembly)? Or can i simply re-compile the xslt and deploy the > assembly > without doing a full application build to release the changes? > I am wondering if i would loose the benefit of just changing the xslt and > overwriting it without any build of the app... > > > "Martin Honnen" wrote: > >> Zest4Quest wrote: >> > I would like to add that i am using the following in my C# code to do >> > the >> > Transform >> > >> > XslCompiledTransform xslTransform = new XslCompiledTransform(); >> > xslTransform.Load(xSLTFileName); >> > xslTransform.Transform(d, null, result); >> > >> > Its taking a few seconds to Transform.The sample given is much smaller >> > than >> > the real ones. >> >> One way to improve performance is to compile the stylesheet with xsltc. >> See >> http://msdn.microsoft.com/en-us/library/bb399405.aspx >> and >> http://msdn.microsoft.com/en-us/library/bb399419.aspx >> >> -- >> >> Martin Honnen --- MVP XML >> http://JavaScript.FAQTs.com/ >> | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
