DLL Hell Help

[Elliot Rodriguez]

I am troubleshooting an existing VB6 application to .NET. Its
incremental, so I've decided to update a specific job from a Forms-based
app to a console-based one, and also, in a reliant VB6 component, change
a single method call from one to another. Pretty simple stuff.

In my .NET app, I set a reference to my updated and compiled VB6
component, and it test for the most part without issue (I work remotely
so my machine does not 100% emulate my development box).

I then send the .NET console app up to my development box and run it,
and it immediately crashes with a QueryInterface error, presumably from
the newly compiled VB6 component.

I was under the impression that as long as the Interop file lives within
the applications root directory (which it does), my .NET app will ignore
the other, older VB6 DLL (its registered as part of a package in
Component Services. I cannot unregister it without first ensuring that
this newer version works). Is the .NET app still looking at the
registered, older version? If so, how can I work around this without
recreating the development box's package?

Thank you for your help

[Mohamoss]

Hi Elliot
did you try to update the reference from the refernce tab within your .net
project to look at the local copy of your DLL
Mohamed Mahfouz
MEA Developer support Center