VS2005 XSLT Debugging with external functions?

Hot Topic

FtpWebRequest GetResponse throw The server committed a protocol violation :(
Security problem with Remoting
Displaying Japanese script
Listbox dropdown SelectedIndex resets after postback
System.Data.OracleClient versus Oracle.DataAccess.Client (ODP.NET)
Web Services .net framework 2
NUnit + AppDomain => ThreadAbortException ?
how to draw barchart in c#asp.net
is it possible to specify "local" as the datasource rather than hard code it?
Problems with .Net 2.0 RC Framework and accessing Performance Counters (specifically Processor)

.NET Development

graphics Override
Convert XML into Pdf Format Using MSXML 4.0 SP2
Query notification Architecture
.Net Programming for the MS Fingerprint Reader (DG2-00002)
Where is mscorcfg.msc(beta 2)?
Getting 0 byte email attachment when constructing attachment using memorystream
BackgroundWorker force cancel
Why do I get Parameter ? has no default value
How do we restrict 3rd party access to an assembly's functionality?
Marshalling COM interface between threads--help!

VS2005 XSLT Debugging with external functions?

Hi

Currently we use visualxslt a plugin that does xslt debugging in vs2003 but from the look of it vs2005's version works a little nicer but.. .

We extensively use EXSLT.net, which is a custom xslt processor that inherirts the .net one and adds new functions for xslt. It there anyway to get VS2005 to use this custom assebly to debug with

Thanks
Brian Norman

Answer this question

VS2005 XSLT Debugging with external functions?

  • sapaplanus

    We will be releasing EXSLT.NET for .NET 2.0 really soon, in a week or so. Then you will be able to debug your stylesheets in VS 2005 for sure.

    Obviously you would need to start debugging from code, by stepping into Transform() method.



  • Denis-D

    Its a shame we cant just choose the processor like we can at the moment in VisualXLT, that is without having to run it through the code just giving it the assembly.

    Brian

  • Glenn N.

    The VS2005 XSLT debugger is based on on the fact that the XSLT is being compiled down to MSIL instructions for execution by the Common Language Runtime.  Any .NET extensions you call from your XSLT can be debugged so long as you have the symbols (.pdb files).  Embedded msxsl:script blocks can also be debugged.  Because of this dependency on MSIL generation, the VS 2005 XSLT debugger does not support plugging in different XSLT processors.
  • VS2005 XSLT Debugging with external functions?
Answer this question