We can debug for example, external assembly’s that are called from within a BizTalk process or debugging pipeline components in run-time mode. In Visual Studio set breakpoints in your code. To debug you must attach to the BizTalk process that is running the .Net code.
- Click on the Debug menu is Visual Studio and select the Process menu item.
- When the Available Processes dialog opens find and select the BTSNTSvc.exe process.
- Click on the Attach button.
If we have more than one host instance configured, when we open the debug menu and choose attach to process, it appears all host instance with the same process name (“BTSNTSvc.exe”), like this:
Determining which process to attach to
Now you need to choose the right BTSNTSvc.exe process by determining the process ID.
You can do this by two ways:
- You can use the TASKLIST command to query the processes. Execute the following command in a command prompt on the remote box:
TASKLIST /FI “USERNAME ne NT AUTHORITYSYSTEM” /FI “IMAGENAME eq BTSNTSvc.exe” /SVC
- Or you can use this application (EnumerateBiztalkProcesses), it shows you the memory consumption and process id of all running BizTalk hosts
Tags: BizTalk | Debug | Visual Studio