I'm exposing a .NET assembly for COM interop, and the assembly version is 2.0.*. I realize that upon compiling and re-registering this forces new CLSID's to be generated for the assembly classes, so it's prone to making duplicate registry entries.
The class in question has a GUID specifically assigned. The assembly has a GUID defined.
I've ready that using the ComCompatibleVersionAttribute fakes the CLSID generation into using a specific version (184.108.40.206 for example). I would have thought that this would not create duplicate registry entries, yet I'm still experiencing the problem.
Obviously I'm lacking something fundamental here, and I'm pulling my hair out trying to figure out how to register an assembly, and if another version of the assembly comes along, NOT have it create duplicate entries in the registry.
I saw this thread but obviously it didn't do the trick. http://social.msdn.microsoft.com/forums/en-us/netfxbcl/thread/54316041-36C0-4666-942D-068A73F4B073
What am I missin
View Complete Post