Hello, Hope you can help. VB6 is not my area. I feel I am missing something simple.
I have a VB6 DLL which I need to place a new version on a machine that will not interfere with the current version.
I can generate the Interop with a new version number which allows me to install it into the GAC.
I also need to Regsvr32 the DLL, and Regasm the Interop.
How do I control the GUIDs that is used for the DLL and Interop?
I have the source for the VB6 component. There is no AssemblyInfo.vb file, I do see that binary compatibility is selected, and it points to a version of the DLL. Is this where it will be pulling the GUID from?
Scanning the code for the VB6 component I see no other references to GUID.
From what I have been reading it appears that RegAsm generates a new GUID on instillation of the interop.
I see parts of the system (an IIS website, that uses java, vb6, vb.net, c#, and DLLs in vb6, vb.net, and c#) that have references to the Interop. The main one is a VB.Net DLL.
How do I make sure that these use the right GUID?
The GAC side is fine, but on my last release it appeared to use the old GUID for regasm/regsvr32 and that caused the old system to pick up the new files which I need to avoid.
I feel I am missing something very simple, if any of my assumptions above are wrong, please tell me.
Also if you could please explain what I am doing wrong or need to do in a very basic way, it would be vastly appreciated.