Hi all

I have a .NET application that is using few ActiveX DLL wrote in VB6. I
managed to get the most from my previous VB6 controls by using them in .NET
but sometimes when I am using my ActiveX DLL in debug mode the associated
Interop DLL in the BIN folder is deleted and my DLL Reference in the .NET
project is broken as I see the Yellow Sign on top of it.

I think that some illegal operation on the ActiveX DLL side may force .NET
to completely remove this Interop DLL from BIN folder?
There is any possible protection against this kind of radical reaction from
..NET side when something get wrong on ActiveX DLL side when use in Debug Mode?

Not only is that Interop DLL deleted but when I try to add it back from Add
Reference my ActiveX DLL that was in the list of References is not there
anymore?

The only way to recover this lost Reference is to Rebuild again my ActiveX
DLL in VB6. After rebuilding this ActiveX DLL then I may get back the lost
Reference and add this DLL to my .NET project.

I am not sure but I have the feeling that this happens only when I am using
that ActiveX DLL in debuging mode and not in Release mode!

My question is anyone experienced this before?

Is that possible that this broken reeference happens also in the field at
customer site with the DLL Released version?


Thanks for all inputs

Sorin