Deploying Custom Pipeline Component on BizTalk Server (PROD)

Deploying Custom Pipeline Component on BizTalk Server:

·        Deploying BizTalk Custom Pipeline Component  on BizTalk Server 2006 or Older Version :

To deploy the custom Pipeline component on BizTalk server 2006 or older version. We need to add the Custom Pipeline component in GAC as well as “C:\Program Files (x86)\Microsoft BizTalk Server 2006\Pipeline Components” folder.

 At design time it will access the Pipeline component dll located in “…..Microsoft  BizTalk Server 2006\Pipeline Components” folder and show the component in pipeline toolbox.

At runtime the BizTalk will use the Custom Pipeline component from GAC.

·        Deploying BizTalk Custom Pipeline Component  on BizTalk Server 2006 R2 or New Version :

To deploy the custom Pipeline component on BizTalk server 2006 R2 or later version. We need to add the Custom Pipeline component only in “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components” folder. No need to GAC this component.

 At design & Run time it will use the Pipeline component dll located in “…..Microsoft  BizTalk Server 2010\Pipeline Components” folder .

Deployment On Production for BizTalk Server 2006 R2 or later version:

1.      Case 1 :  Custom Pipeline component dll added to GAC but not located in “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

At runtime the Biztalk process will first try to find the dll in “Pipeline Component” and if it does not find it in this folder then check the dll in GAC. Once it find the dll in GAC, it will use it. Process won’t give any error.

2.      Case 2 :  Custom Pipeline component dll added to folder “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components” but not in GAC

At runtime the Biztalk process will first try to find the dll in “Pipeline Component”. As it find the dll in ‘Pipeline Component’ folder won’t go to GAC, it will use the dll located in GAC. Process won’t give any error.

3.      Case 3 :  Custom Pipeline component dll  neither added in  GAC nor in folder “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

At runtime the Biztalk process will first try to find the dll in “Pipeline Component” and if it does not find it in this folder then check the dll in GAC. The process will also not able to find the Custom Pipeline component dll in GAC. This time the process will throw the error “ Custom Pipelince component  ‘Assembly Name’ not found in C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

From BizTalk Server 2006 R2, we don't have add the Custom Pipeline component in GAC.

The Default expected location for this dll is  “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

And if it does not find the dll at this location then it will check assembly in GAC.