The Ramblings of Two Microsoft .NET Developers, TFS, and Visual Studio ALM Guys --- "Yes, we are both named Ed."

BizTalk 2004 Debugging



Debugging .Net assemblies can be tricky in BizTalk 2004. When working with Orchestrations you need to make sure that the version of the Orchestration dll and .Net assembly corresponded. There are two way in which to do this and be able to debug successfully.

 

1. If your Orchestration project and .Net assembly project are in the same solution. Build/Rebuild solution that contains the Orchestration project and your .Net assembly project. Make sure your .Net assembly project is in debug mode. This can be configured in the 'Configuration Manager". Then, Delete their dll from GAC and install the new ones. Now you can debug by attaching to the process "BTSNTSvc.exe".

 

2. If your Orchestration project and .Net assembly project are in different solutions then you will need to change the versioning from the default VS configuration. To change this, open your projects "AssemblyInfo.cs" file and change [assembly: AssemblyVersion("X.X.X.*")] to a hard coded value such as[assembly: AssemblyVersion("1.0.0.1")]. Make sure your .Net assembly project is in debug mode. This can be configured in the 'Configuration Manager". Then, Delete their dll from GAC and install the new ones. Now you can debug by attaching to the process "BTSNTSvc.exe".

 

 

Ed K.

Posted in


Name
E-mail
(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