Geeks With Blogs

News
Stuart Brierley Integration Management - BizTalk and More

If you want to debug your custom pipeline component you can make use of the Pipeline.exe utility to do this:

  • Set the breakpoint in your Custom Pipeline Component code in Visual Studio.
  • On the properties page of the project containing your Custom Pipeline select the Debug tab.
  • Set the “Start Action” property to "Start external program" and then type or browse to:

{Installation Location}\Microsoft BizTalk Server 2010\SDK\Utilities\PipelineTools\Pipeline.exe

  • For the "Start Options > Command line arguments" property type:

{PipelinePath}\{PipelineName}.btp -d {MessageInstancePath}\{MessageInstanceName}.xml -c

  • Now, just press F5.  The chosen pipeline will be run and the breakpoint in your Custom Pipeline Component code should be hit, allowing you to step through and debug your code.

As far as I am aware your Custom Pipeline Component and your Custom Pipeline must be in the same solution, although they can of course be in seperate projects.

Note: Pipeline.exe will not execute properly if your Custom Pipeline is using the Flat File Assembler / Disassembler Pipeline Components.  In such cases you will need to create a test Pipeline that excludes these pipeline components. 

Posted on Friday, November 4, 2011 12:31 PM BizTalk Pipelines | Back to top


Comments on this post: BizTalk 2010 - Debugging Custom Pipelines Components

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Stuart Brierley | Powered by: GeeksWithBlogs.net