Debugging legacy ASP application on VStudio under XP SP2

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mukesh bhakta - 24 Oct 2005 23:21 GMT

Hi guys,

I have a rather strange problem with debugging a legacy ASP project
that uses COM Interops written in VB.NET.

The project when debugged on Win2000 allows JIT debugging of the CLR
code using the DefaultDomain in the 'Debug Processes' dialog. I also
see two DLLHost instances that can be used for debugging.

Under XP the same code only allows stepping into ASP and T-SQL code but
the CLR code cannot be debugged. I only see one DLLHost instance with
no 'DefaultDomain' in the debug process dialog.

I have checked DCOM settings et al coming from the MSDN KB's but still
no luck. All security settings on both machines are ditto.

Any suggestions?

Cheers

MB

Reply to this Message

Robert Jordan - 25 Oct 2005 00:07 GMT

> Hi guys,
>
[quoted text clipped - 8 lines]
> the CLR code cannot be debugged. I only see one DLLHost instance with
> no 'DefaultDomain' in the debug process dialog.

Under XP and 2k3 the CLR gets loaded on demand, so you
cannot attach to dllhost.exe before the COM object has
been created *and* before one of its methods has been
accessed.

Rob

Reply to this Message

mukesh bhakta - 25 Oct 2005 05:12 GMT

Hi Rob,

The COM controls do the rendering of the page contents and i can see
all values coming from the controls but still cannot 'breakpoint' or
trace into the code.

Cheers

MB

Reply to this Message

Rate this thread:

Debugging legacy ASP application on VStudio under XP SP2

Free Magazines