Custom Pipeline Component Cann't be added Toolbox

annot add (custom) pipeline component to the toolbox (You have selected an invalid pipeline component assembly. Please check security settings for the assembly if you are loading it from an UNC path)

Thanks to ... Patrick Wellink

If you created a pipeline component with the Pipeline componet wizard it will probably run just fine.

But then comes that moment in time that yoy want to create a new pipeline component that looks just like an already created pipeline, so you decide to copy the code and change some things.
Then you compile the component and you try to add it to the Vizual studio toolbox. And then you get the following message :

You have selected an invalid pipeline component assembly. Please check security settings for the assembly if you are loading it from an UNC path.

Well, you can check whatever you want but it probably won't help.

Possible causes are :

1. Your Pipeline uses some DLL that's not in the GAC or pipeline components folder.

2. There is something wrong with the namespaces..... That's what I am going to cover now.

A pipeline component has the following piece of code...

 private System.Resources.ResourceManager resourceManager = new System.Resources.ResourceManager("BizTalk.BestPractice.PipelineComponents.AuditingComponent", Assembly.GetExecutingAssembly());

For descriptions and stuff, the pipeline uses a resource file. The piece of code above tells the pipeline component where the resource file is located. 
If the namespace and component name are not exactly the same as the namespace and component name mentioned in the piece of code above you will get that message.

I saw several questions about this in google but none had this solution, so I figured this blog entry would maybe come in handy for someone with the same problem.