Ahem. It turns out that I was referencing the wrong version. I'm good now.



>>Make sure that any dlls that the external dll depends on are also available where it is being used. i.e if you are referencing A.dll and it depends on B.dll check that there's also a reference to B.dll in the main project...
>
>It seems that the client project does reference A, but all its (public) classes. If the classes are declared public that should do no?
>
>Perplexed here because I was hoping to use some lower level classes that were developed in vb referenced from a new project I intended to write in C#, be it only to overcome my aversion for curly braces. :)