I installed this on a 4.5.2 site. Seems that everytime I included an xsl:include file and then made a change, IIS would crash. I'd reboot IIS and the change would work fine. Up until I made the next change.
Removed my xsl:includes and now everything is working fine.
I thought this was what XSLTouch was supposed to help with, but I could be mistaken.
So unfortunately, I've figured out that XSLTouch is the source of my pain.
I removed all of my includes from files, and it still crashes my IIS. I remove the .dll from my bin folder and everything works great. I add include files into the xsl, and touch both files, and they work. No crashes.
Use that same file and add the .dll back into the bin. Crashes IIS.
Locally, I'm using XP. Our staging server is IIS 7.
Apparently, this was an issue with XSLTouch and the way one of the .xsl files from Blog4Umbraco was saved. The BlogTagCloud.xslt was not saved as an ansi file. When it is converted to ANSI, it displays some strange characters that needed to be removed. Once they were removed. Voila. Everything works again.
Glad it's working for you now Chad, was pure coincidence that I read about file encodings the other day, otherwise I would never have thought of checking the file!
Hey Chad, new version is up on the package repos (http://our.umbraco.org/projects/developer-tools/xsltouch) can you reinstall and give it a whirl for us? We've tested it at this end and seems to be doing as it should, would be nice to have some "in the wild" testing too.
IIS Crashes
I installed this on a 4.5.2 site. Seems that everytime I included an xsl:include file and then made a change, IIS would crash. I'd reboot IIS and the change would work fine. Up until I made the next change.
Removed my xsl:includes and now everything is working fine.
I thought this was what XSLTouch was supposed to help with, but I could be mistaken.
-C
So unfortunately, I've figured out that XSLTouch is the source of my pain.
I removed all of my includes from files, and it still crashes my IIS. I remove the .dll from my bin folder and everything works great. I add include files into the xsl, and touch both files, and they work. No crashes.
Use that same file and add the .dll back into the bin. Crashes IIS.
Locally, I'm using XP. Our staging server is IIS 7.
I'm using 4.5.2.
-C
Apparently, this was an issue with XSLTouch and the way one of the .xsl files from Blog4Umbraco was saved. The BlogTagCloud.xslt was not saved as an ansi file. When it is converted to ANSI, it displays some strange characters that needed to be removed. Once they were removed. Voila. Everything works again.
Glad it's working for you now Chad, was pure coincidence that I read about file encodings the other day, otherwise I would never have thought of checking the file!
Chad just out of interest what version of .net where you running? I've got a fix for .net 4 setups coming out in a minute.
Was using 3.5.
Hey Chad, new version is up on the package repos (http://our.umbraco.org/projects/developer-tools/xsltouch) can you reinstall and give it a whirl for us? We've tested it at this end and seems to be doing as it should, would be nice to have some "in the wild" testing too.
Cheers
Pete
Would love to give it a shot, but I'm using Umbraco 4.5 with ASP.NET 3.5.
It doesn't look like there is a version for that.
-C
The DotNet2 version should run for you on 3.5, its the same framework just with some goodies added. .net 4 though is a whole new framework.
is working on a reply...