Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
how to debug com component from asp
- Thread starter Jeet2004
- Start date
Cagliostro
Programmer
you should put breakpoints in your VB project, and attach runtime VisualStudio (with loaded project) to the IIS process. After that launch the ASP page by requesting from a local or remote browser(anyway you should use internet address). When you finish, stop IIS and detach VisualStudio.
Ion Filipski
Ion Filipski
- Thread starter
- #3
I figured out another simple way.Its working great where i have my page and component on my local machine.
You unregister the component from the local machine and run the project in vb IDE and then launch the page on the machine. It will stop where the breakpoints are in the component and let you debug.
Thanks for your help IonFilipski.
You unregister the component from the local machine and run the project in vb IDE and then launch the page on the machine. It will stop where the breakpoints are in the component and let you debug.
Thanks for your help IonFilipski.
Jeet,
I am facing a similar problem. I want to debug a DCOM component in VB 6.0 from an ASP application.
I unregistered all DCOM entries and ran the VB app with breakpoints. This creates an entry in DCOMCNFG with the application path. But the ASP application doesn't recognize the copy of DCOM in memory and I cannot debug.
Please help.
I am facing a similar problem. I want to debug a DCOM component in VB 6.0 from an ASP application.
I unregistered all DCOM entries and ran the VB app with breakpoints. This creates an entry in DCOMCNFG with the application path. But the ASP application doesn't recognize the copy of DCOM in memory and I cannot debug.
Please help.
- Status
Similar threads
- Locked
- Question