Debugging COM .DLL from VB.NET

[JLin88]

Hi all:

Sorry if this is a repeat or if this has been discussed already (searching didn't show anything relevant).

QUESTION:

Is there a way to debug a COM .DLL file that is being referenced by a .NET solution? In other words, I have a .DLL file that was written in VB6 (which I have the code for). In my VB.NET solution, I am referencing this .DLL.

Is there any way to set it up so that I can see and step through the VB6 code for this DLL when I run my VB.NET solution?

Thanks very much in advance.

Jason

[Edneeis]

You can't debug the COM DLL in the .NET environment (IDE) that I know of. What you can do is - Start debugging in the VB6 IDE ,with the COM DLL code loaded, this should bring up a dialog that has the option 'Wait for components to be created', choose that and then fire up the .NET app that uses the DLL and it should automatically debug it. I do this all the time for Word and Office Add-Ins. Its a good idea to set a breakpoint in there to test or help. The only thing to remember is that the DLL instance must be created AFTER you start the debugging in the VB6 IDE.

[JLin88]

Thanks a lot ... that worked.

[brookema]

Is there a way to do the reverse? Debug a COM .DLL written in VB.NET that is used by a VB6 program?

[Edneeis]

I haven't tried it but the samething should work. Fire up VS.NET and run the dll then run the VB6 app that uses it. You may have to set the 'Start external application' options in the configuration manager properties.