By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,996 Members | 1,095 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,996 IT Pros & Developers. It's quick & easy.

Debugging .NET DLLs called from COM objects.

P: n/a
I have a .NET DLL, which is called from a COM object (interop).

I want to debug the .NET DLL and the COM DLL in their respective IDEs.

So, in the .NET DLL, I set the debugging start application to be VB6.exe. I
hit F5. VB6 runs up. I open the COM project, and then hit F5 to run it.

Result : VB6 just disappears, no messages, no errors, no pack drill. Even
the output window in the .NET IDE is blank.

Can anyone give me a hint as to why VB6 just vanishes, or how I can get
either VB6 or IDE.NET to let me in on their secret as to why they collapse.

What's even more annoying; until very recently, this used to work. So, the
VB6/IDE.NET relationship is getting tired.

Much obliged.
Gem
Mar 30 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.