But if i import a xslt file, and make changes to the imported xslt file, i have to either touch web.config/recykle appPool/restart website for the changes to take effect.
Is there any way i can fix this, my development time is increased to much, if i have to restart the app for each change.
"Automatically "touches" the modified date of any XSLT files that include a child XSLT file when that child is saved. This causes .net's XSLT cacher to refresh both files to ensure that what you see when you next run it is what you expect."
Dan is right - XSLTouch fixes that exact problem and it is awesome at that. You *can*, however, fix it by saving touching/saving the master XSLT file, but after doing that once or thrice you just don't want to deal with it anymore.
xsl:import requires application restart for changes in imported xslt to display
Hi.
Iam using xsl:import, for reusing my templates.
But if i import a xslt file, and make changes to the imported xslt file, i have to either touch web.config/recykle appPool/restart website for the changes to take effect.
Is there any way i can fix this, my development time is increased to much, if i have to restart the app for each change.
Best regards, n thx in advance
Jacob.
Yeah, that can be a pain. Maybe this package would help you - http://our.umbraco.org/projects/developer-tools/xsltouch ?
"Automatically "touches" the modified date of any XSLT files that include a child XSLT file when that child is saved. This causes .net's XSLT cacher to refresh both files to ensure that what you see when you next run it is what you expect."
Dan is right - XSLTouch fixes that exact problem and it is awesome at that. You *can*, however, fix it by saving touching/saving the master XSLT file, but after doing that once or thrice you just don't want to deal with it anymore.
Go go go ! :-)
/Chriztian
But iam not writing my xslt in umbraco admin, iam using vs2010, the package expects iam using the umbraco admin to edit xslt, right ?
Hi Jacob,
Not at all - in fact there's a standalone console version if you need it for other .NET projects.
I edit all my XSLT on a MacBook Pro and just hurl 'em to the site via FTP - XSLTouch just works. It's brilliant :-)
/Chriztian
is working on a reply...