Recently I developed a custom pipeline component, this component as a specified characteristic: it used a third-party DLL (provided by the client).
After successful compilation, the ALL assemblies must be put on “C:\Program Files\Microsoft BizTalk Server 2006\Pipeline Components” folder (Alternative: put component DLL in pipeline Components folder and the third-party DLL in GAC)
But, while adding the component in the VS toolbox, I was surprised with the following error:
“You have selected an invalid pipeline component assembly. Please check security settings for the assembly if you are loading it from an UNC path.”
- First, check that your pipeline component class is public.
- Also, make sure any assemblies you reference from the custom pipeline component are in the GAC or Pipeline Components folder (if that’s where you drop your custom pipeline component assembly).
- Check for missing dependencies, they all have to be put on GAC or Pipeline Components folder
In my case, the DLL that I try to used (that was provided by the client), I success build the solution (without error or warning) in Visual Studio, but when I checked the DLL have some dependencies that weren’t installed in GAC (in my case nunit.framework.dll version 18.104.22.168).
I install dependencies in GAC and solved the problem.