I enjoyed Chp 24 Using Business Objects, and the simple example on how to create and call a legacy business object, but the real world problem I'm dealing with is how to step into and debug the VB6 COM DLL that I have (it's our own DLL so I have the source code).

Does anyone have the documented steps on how to do this? The Help in VS 2005 is seriously lacking IMHO. My VS 2005 ASP.NET project is pointing to IIS (HTTP system setup in the New Project dialog). And the VB6 COM ActiveX DLL is SP5. My OS is XP Pro.

As it is now I'm hitting the call to the DLL and creating the object no problem and I'm calling the method I need in that COM component, but obviously in the COM object something is not quite right, because what should take a minute to run is churning and churning to the point where I eventually have to kill it.

This might be helpful:

http://blogs.msdn.com/robgruen/archi...09/254602.aspx

Although it was meant for VS2003, you should be able to do the same stuff in VS2005 (debug unmanaged code, load symbols, etc)

Devin

Thanks, I did read that article, but already by Step 3 I'm stumped "...select the “Configuration Properties->Debugging” property page and enable unmanaged debugging." because I don't find anything remotely similar to "unmanaged debugging" anywhere in VS 2005.