I'm trying to debug a legacy VB6/ASP/COM+ application using Visual Studio 2010. The COM+ DLL has been compiled with full debug information and has the corressponding .PDB files. I attach to the dllhost process of the COM+ component and during execution when an exception is thrown, I'm unable to see the details of the error in the debugger.
Typing Err into the immediate window displays 0. Typing Err.Description displays CXX0025: Error: operator needs class/struct/union.
The locals window doesn't show any error or exception information. How can I view the details of a thrown exception?
Update
I'm still not able to view error information or properly inspect variables and objects. I'm also using Visual Studio 2010 to debug the classic ASP pages (VBScript) parts of the application and it seems to have a full featured debugging experience, i.e. I can inspect variables and objects properly. Since classic ASP with VBScript is a close cousin of VB6 and they're both COM based, should I not be able to inspect VB6 errors, variables and objects properly too?
You normally need an IDE for the langauge it was originally written in so VB6 for the VB6 components, VS6 for the ASP components?