I have built a managed wrapper class and assembly that expose much
functionality available in unmanaged legacy DLLs. I can write VB apps that
interface with the managed assembly, and the managed assembly makes calls to
the legacy dlls. All seems to work fine when the assembly is a private
assembly. When I go through the process of strong naming the assembly and
placing it into the GAC, none of my VB apps will initialize. I have gone to
each of my VB apps and referenced the now strong named assembly, but no luck.
I have specified in my VB references to not "copy local" the strongly named
assembly. The mixed language (managed/native) assembly is written in C++,
and all projects are built with VS2005. I've written a C++ client, and see
the same behavior when I try to access the mixed assembly. Any ideas?
