XSLT Debugging with .NET

November 10, 2008 · 1 min read

Over the years debugging XSLT has gotten better and better but one thing continues to be lacking. XSLT debugging with.NET component references in the XSLT. I know there are some tools that do a decent job but something is always lacking.

Well I decided to write an XSLT debugger that uses Visual Studio. It is fairly easy to use and is very robust. I will put pictures and such up later but for now I just wanted to get the app out. So if you are like me and are looking for a debugger that includes.NET capabilities then here it is. If you have questions feel free to ask.

So here it is... (Drum Roll)

The XSLT Debugger for.NET.

 So I added an example application that is located in the install directory

C:\Program Files\XSLTDebugger\ExampleApplication

Here are the instructions: 1. Start application - XSLTDebugger.exe located C:\Program Files\XSLTDebugger\ by default. 2. Follow instructions on the screen, adding input, xslt, and output files. 3. The Arguments are the most important part. The arguments represent the.NET component itself. So reference your.NET component and then choose the appropriate "type" or method call. Make sure that the assembly you reference is in the GAC and is strong named. 4. The namespace field is what is referenced in the XSLT. An example is: xmlns:inputHelperObj=

Enjoy.

5. The Type field and the Namespace field basically coorelate to each other thus providing the reference. 6. Make sure you add the arguments to the list and repeat for each argument you need to add. 7. Once done click debug, you will get the screen that says which environment do you want to open. This is normal and is how you debug in visual studio so if you have Visual Studio 2005 choose the Visual Studio 2005 environment. 8. Any questions just ask. I will try to respond quickly.

This article is part of the GWB Archives. Original Author: Mark Wiggins

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.