BizTalk – How to debug Custom Pipeline Components running on Isolated Host

Posted: May 8, 2011 in BizTalk
Tags: , , ,

Normally we can debug almost all pipeline components in run-time mode by attaching Visual Studio to “BTSNTSvc.exe” process (see: Debugging External assembly’s or pipeline components – Attach to Process – which BizTalk process to use?)

This is true for components that is running on In-Process Host, the exception is: Custom Pipeline Components that are running on Isolated Host.

One of the differences between Isolated Host and In-Process Host is that an Isolated Host must run under another process, in most case IIS, and an In-Process host is a complete BizTalk service alone.

So, if you are using custom pipelines that are associated, for example with HTTP, SOAP or WCF Adapter, then you need to attach to the proper isolated host process, in this case “w3wp.exe” process.

Note:

The application pool process (w3wp.exe) is typically not started until the first request is received.

You can use a browser to access the receive location URL, this should return a WSDL and should cause the “w3wp.exe” process to initiate.

Related articles:

Special thanks

One of the pleasures of trying to help other people’s is that sometimes you learn some things, and this is one of these cases , thanks Ritesh.

Tags: BizTalk | Pipeline | Components | Debug

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s