On Tue, Mar 17, 2009 at 11:44 AM, Ruben Willems <[email protected]> wrote: > Hi > > > you already compile the VB6 code, correct? > so this provides you with a dll, or exe or something that has to be called > by .Net, correct? > > you can create the interop by hand, and sign it also > the utility you need is : tlbimp > you can find it under C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin > > tlbimp VB6.dll /primary /keyfile:"myKey.snk" /out:theNewOne.dll > > > copy this one in your lib folder, and it should go
Ruben - thanks kindly for the speedy reply. This is half of the problem, but the other half is extracting the GUID from the "theNewOne.dll" and updating the reference in the csproj file to reflect the dll's new GUID. The underlying problem is that VB6 dll's regen their GUID's everytime they're built - a primitive form of versioning I suppose. Gross Mark Blog: http://www.notesfromatooluser.com/ Recent Entries: Agile/Scrum Smells: http://www.notesfromatooluser.com/2008/06/agilescrum-smells.html Agile Games for Making Retrospectives Interesting: http://www.notesfromatooluser.com/2008/10/agile-games-for-making-retrospectives-interesting.html
