Entry

How to debug an assembly called by Orchestration

Apr 6th, 2005 22:25
Balaji Ramachandran, http://www.netologi.se/default.aspx?Contents=BizTalkFAQ

When a BizTalk component, pipeline component or orchestration, is 
deployed it references specific version of each of its dependent 
assemblies. If the version number does not match exactly the assembly 
will not be loaded, and if there are multiple versions available only 
the exact match will be loaded even though there are newer versions 
available. This is the normal behaviour for .NET! 
A common mistake when you try to debug an assembly that is executed by 
BizTalk is that you debug the wrong version. This may be due to that 
the version number is changed each time you rebuild your project, this 
is controlled by the 1.0.* in AssembyInfo.cs. You will avoid problems 
by hard-coding the version to 1.0.0. 
To actually put a break point in your dll - here is what you need to 
do: 
Build and GAC a debug version of your assembly. 
Restart BizTalk service (BTSNtSvc.exe) 
Attach VS.NET debugger to BTSNtSvc.exe and put a break point in your 
code. 
Run your orchestration.