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 with kind regards Ruben Willems On Tue, Mar 17, 2009 at 4:24 PM, Mark Levison <[email protected]> wrote: > Please forgive this posting I realize its completely off topic - but I'm > hoping that someone on this list has had experience trying to do automated > builds that included references to VB6 projects that themselves have to be > built. A few hours of googling hasn't even found someone with the same > problem (which clearly means I'm using the wrong word > > > The team I'm coaching is building an ASP .NET app (VS 2005) that has to > work within an existing VB 6 application. As such they created an Interop > dll written in VB6. So far so good, the problem comes when the interop dll > is added as reference in the application. When the dll is rebuilt the > projects reference to the dll is wrong (incorrect GUID I think). > > So how do you solve this problem? > > - build the dll in prestep and magically update the csproj file? > - use msbuild to help magically recreate the csproj file? > > I guess I'm looking for the magic part - how to update the reference? > > Cheers > 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 > > >
