Article ID: 299633 - Last Review: May 29, 2006 - Revision: 5.1 How To Debug Visual Basic COM Components That Are Used Within Active Server PagesThis article was previously published under Q299633 On This PageSUMMARY
This step-by-step procedure demonstrates how to debug (or step through) Microsoft Visual Basic (VB) Component Object Model (COM) components that are used within Active Server Pages (ASP) pages. Debugging VB COM Components That Are Used in ASP Pages
TroubleshootingIf you are already running a compiled version of this dynamic-link library (DLL) from this ASP page, you may not hit the breakpoint. In this scenario, you may want to stop and restart Microsoft Internet Information Server (IIS) services. To do this, on the Windows Start menu, click Run, and then type IISRESET. Please note that this command stops and restarts IIS, as well as all IIS applications that are running.REFERENCES166275
(http://support.microsoft.com/kb/166275/EN-US/
)
How To Debug a Native Code Visual Basic Component in VC++
264957
(http://support.microsoft.com/kb/264957/EN-US/
)
BUG: VB DLL Has Memory Leaks and Crashes in COM+ if 'Retain In Memory' Not Set
259725
(http://support.microsoft.com/kb/259725/EN-US/
)
PRB: Error Occurs When You Debug a COM+ Component Under the Visual Basic IDE with an ASP Client
265492
(http://support.microsoft.com/kb/265492/EN-US/
)
BUG: ObjectContext Item Collection Is Empty When You Debug Under COM+
244457
(http://support.microsoft.com/kb/244457/EN-US/
)
How To Debug an MTS VB Component Running Under ASP
APPLIES TO
| Article Translations
|

Back to the top
