We spent more and more time struggling with the limitations of the Microsoft XSLT 1.0 processor. I think it's time to start using XSLT 2.0. Saxon seems to be a good choice. The problem is that the Visual Studio built-in XSLT debugger is great and no one wants to stop using it.
My question is , is there a way to provide my own processor for using Visual Studio? Even if the step-by-step debugging didn’t work, it would still be great to have XSLT from Visual Studio (Alt + F5) work instead of adding any other software package to our workflow. It seems unlikely that Visual Studio will do this out of the box, but does anyone know an extension that can help?
Otherwise, is there a good free debugger that works with Saxon and is similar to VS-one?
I really want to start using 2.0; this will save us a huge amount of time and complexity, but the thought of the need to use an additional editor makes people persistent. Any ideas? Convincing arguments that I can use?
source
share