.comment-link {margin-left:.6em;}

Ben Cops

Tuesday, February 14, 2006

You have selected an invalid pipeline component assembly

When adding a pipeline component to the toolbar, the IDE checks the component, and apparently runs through all its dependencies. If it can't resolve a dependency somewhere either through the GAC or in the same folder (normal probing rules) you get an error on attempting to add the component:

You have selected an invalid pipeline component assembly... <then some red herring about security on UNC paths>

You also get this error if you've not marked up your pipeline component properly - the component must have the following attribute on the class!

[ComponentCategory(CategoryTypes.CATID_PipelineComponent)]

*DOH*

posted by Ben Cops at 12:15 pm

10 Comments:

  • I encountered the same error message when adding a custom pipeline component for a client. It actually turned out to be a namespace issue here.

    By Anonymous Anonymous, at 9:32 pm  

  • Make sure your class is public, that caught me out.

    By Anonymous Anonymous, at 4:56 am  

  • You will also get this if you reference (ie inherit) from a class in a different assembly. We have a generic pipeline class we inherit from in a shared assembly. If it can't find this assembly you will get this error.

    By Anonymous Anonymous, at 2:03 pm  

  • The same error message is thrown if the GUIDs in AssemblyInfo.cs, the GetClass() method and in the class settings are not the same.

    By Blogger Christoph, at 11:06 am  

  • Set all 3 guids to the same-thing, still same error...

    Was trying to GAC and unGac it, no esternal dependencies; name space is correct for the resource file and the Class attributes are in place.

    What else am I missing???
    It was regestering once, then after few rebuilds and increasing the asembly info version, it got screwed... Adn I don't see any real changes other then in Execute method...

    By Blogger puzzled, at 9:33 pm  

  • I discovered that there is a limitation to the length of either the namespace or the ResourceManager.
    Try making the namespace as short as possible and try again (remember to update the code that loads the ResourceManager)

    By Anonymous Abimov, at 2:42 pm  

  • not using the wizard and creating one from scratch the class will not have the public in front by default

    By Anonymous Anonymous, at 2:47 am  

  • Also, make sure the required dll's (Interop.SSOClient / Messaging / Pipeline / Streaming / TestTools) belongs to same BizTalk Server version, you are using for development.

    By Blogger harry, at 7:37 pm  

  • Also, make sure the required dll's (Interop.SSOClient / Messaging / Pipeline / Streaming / TestTools) belongs to same BizTalk Server version, you are using for development.

    By Blogger harry, at 7:38 pm  

  • Yes, the limitation is 50 characters. When creating ResourceManager, the baseName argument shouldn't be longer than 50 characters. Funny.

    By Anonymous Laszlo, at 4:54 pm  

Post a Comment

<< Home