Debug that BizTalk Map

Ouch! Look at this map. I need to see what is happening in some of these functoids. What is a developer to do?????


A map is just complex XSL.... So to debug the functoids we need to treat it as such. First, lets Validate our map and get the location of the XSLT.


Since it validated (no errors) we have the XSLT output location in the Output Window. Copy this location to your clip board. 


Open the file with Visual Studio:


Now, right click on your XSL working area and select properties. Here you will enter the input file that will be used for the transform:

Mark your break points, just as you would a code file, and start the debug:


Now you can step through just as if it was .Net code:


Even step into the functoid code:



Ed K.

Technorati Tags: ,
Posted in

Monday, 22 April 2013 09:22:16 (Pacific Daylight Time, UTC-07:00)
When you do a complicated map, use tabs to seperate them Map with Biztalk 2010 is much more user friendly.
Recommend using XSLT in functoids as they are lightweight and never get compiled like C# code. Tabbing makes map looks simplified. You click on any element an indicator shows which tab the element is mapped.

(will show your gravatar icon)
Home page

Comment (Some html is allowed: a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

[Captcha]Enter the code shown (prevents robots):

Live Comment Preview