COM classes are globally registered in the Registry. To do this, they need a unique ID - a GUID.
By default, .Net classes are not globally registered. To do this, you must place the assembly in the GAC (the equivalent of the registry) and give it a strong name (the equivalent of a GUID). Richard > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of > Patrick Burrows > Sent: 31 May 2002 14:22 > To: [EMAIL PROTECTED] > Subject: [DOTNET] COM Interop calling a C# DLL from VB6 > > > Ok... I guess I'm not understanding what a strong name is (in .NET > terms). Why do I need a snk file? All I want to do is call my C# DLL > from VB6. > > I use sn.exe to create an SNK file. And I set AssemblyKeyFile and > AssemblyKeyName properties. But it is still saying my Assembly doesn't > have a strong name. > > And I *truly* don't understand what any of this has to do with COM > interop. What does some sort of public key encryption have to do with > COM? > > > Patrick Burrows > What's he building in there? > -------------------- > Now Playing: unknown artist - frank sinatra - 05 - the way y (patcast) > -------------------- > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
