LOL--OMG, nevermind on this thread. I am such an idiot. I had my DLL and a test EXE in the same solution.
I had been changing the AssemblyInfo on the test app, not on the DLL. *That's* why it kept telling me it wasn't named strongly. D'oh! FWIW, Just checking off the "Register for COM Interoperability", filling in AssemblyKeyFile and AssemblyKeyName with valid info, and adding "[ClassInterface(ClassInterfaceType.AutoDual)]" to the class you want to expose works just dandy. There's obviously more to it to learn... it actually exposes too much stuff, for instance. But I got passed this little bit of idiocy. Patrick Burrows Police at the station And they don't look friendly -------------------- Now Playing: various artists - fuel 2000 - one way out - elmore james (patcast) -------------------- > -----Original Message----- > From: Patrick Burrows > Sent: Friday, May 31, 2002 11:31 AM > To: [EMAIL PROTECTED] > Subject: Re: COM Interop calling a C# DLL from VB6 > > > FWIW, I just found > http://www.codeproject.com/dotnet/cominterop.asp#PART2 > > Which seems to be a very good and detailed discussion of doing COM > interop. I'm about to sit down and read it, but from the sample I just > looked at, there is nothing in there at all about needing .SNK files. > > Patrick Burrows > In this sinking board walk town > -------------------- > Now Playing: no artist - audiotrack 11 (patcast) > -------------------- > > > > > -----Original Message----- > > From: Brent E. Rector [mailto:[EMAIL PROTECTED]] > > Sent: Friday, May 31, 2002 11:11 AM > > To: [EMAIL PROTECTED] > > Subject: Re: COM Interop calling a C# DLL from VB6 > > > > > > The docs are wrong when the claim a .NET assembly used via > COM interop > > must have a strong name. As you state, they only need a > strong name in > > order to be added to the GAC. As long as you understand the assembly > > search rules, you can use an assembly via COM interop (i.e. by a COM > > client) by placing the assembly in the client's private > > assembly search > > path. > > > > -- Brent Rector, .NET Wise Owl > > Demeanor for .NET - an obfuscation utility > > http://www.wiseowl.com/Products/Products.aspx > > > > > > > > -----Original Message----- > > From: Richard Birkby [mailto:[EMAIL PROTECTED]] > > Sent: Friday, May 31, 2002 7:41 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [DOTNET] COM Interop calling a C# DLL from VB6 > > > > > > 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. > > > > 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. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
