Debug maps in BizTalk 2006/2006 R2 and in BizTalk 2009

  • Sandro Pereira
  • Aug 7, 2009
  • 2 min read

This is a great feature that, in most cases, is overlooked, because maps can become very large, to the point that it is difficult to read, very difficult to maintain, and detect some problems.

For many, the ability to debug maps is a new feature in BizTalk Server 2009, because it finally has a particular emphasis on the Menu, but that is not true, because BizTalk Server 2006 R2 or even BizTalk Server 2016 will also have the same capability.

📝 One-Minute Brief

Debugging maps in BizTalk has evolved, but the core principles remain. This post covers the essential steps for debugging maps in BizTalk 2006/2006 R2 versus BizTalk 2009. While the older versions required manual XSLT extraction and debugging in Visual Studio, BizTalk 2009 introduced the powerful Debug Map feature directly in the IDE. This guide ensures you know how to set input/output instances and step through your XSLT and C# functoids to find and fix transformation errors quickly.

Debugging maps in BizTalk Server 2009

  • Right-click on the map file, and now you have a new Item “Debug Map”, next to “Test Map” and “Validate Map” items
Debug Map inside Visual Studio

You will get the possibility to debug the actual XSLT that BizTalk generates and also the possibility to debug scripts, functoids, and other custom code.

Debug Map inside Visual Studio

Debugging maps in BizTalk Server 2006 or 2006 R2

Visual Studio 2005 has a great feature that enables you to debug BizTalk Maps:

  • Right-click the BizTalk map and select Validate Map.
  • In the output window, you’ll see a link to the .xsl. Click on the link to bring it up in VS.
  • Right-click the .xsl and select View Source.
  • At that point, you can set breakpoints in your .xsl.
  • Then select XML > Debug XSLT – at which point you’ll be able to step through the XSLT.

ebugging isn’t just for fixing bugs; it’s for understanding performance. By stepping through the XSLT, you can identify redundant loops or heavy scripting functoids that might be slowing down your production environment.

Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son. 

Thanks for Buying me a coffe
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *

The Ultimate Cloud
Management Platform for Azure

Supercharge your Azure Cost Saving

Learn More
Turbo360 Widget

Back to Top