I am doing this using Visual Studio 2005 and BizTalk 2006. Unfortunately, that is the environment at my client.
Open your pipeline component project is VS. Be sure it is the same you used when you created the pipeline that is deployed to BizTalk Server 2006.
On the "Attach to Process" dialog:
- Click the "Select" button near the "Attach to" text box and select "Managed Code" and "Native Code". Not sure you need native code here, but I selected it and it worked.
- Check the "Show processes from all users" and "Show processes in all sessions" checkboxes.
- Click the "Refresh" button.
You should be able to see the BTSNTSvc.exe process in the "Available Processes" grid. Go ahead and attach to that process. If you are debugging a receive pipeline that receives HTTP you might have to attach to w3wp.exe instead.
You are now attached. You are likely to want to put a break point on the "Execute" method and go from there.
Run a test message and you will get a break on your break point.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.