in visual studio 2008, when I stop debugging an asp classic website visual studio always crashes

Question

We are running visual studio 2008 (with the service pack) and having troubles when we are debugging an asp classic website.

The server is windows 2003 sp2. We are using windows authentication. We have a virtual directory that is an asp.net web application.

We can attach to the w3p process and debug just fine. breakpoints work, we can view variable values. The difficulty arises when it comes time to detach or stop the debugger.

Every time we take either approach (detach or stop the debugger) we get a series of crashes from Visual studio.

I just separated the website into its own app pool and got the following error in the event log when I detached the debugger:

.NET Runtime version 2.0.50727.3607 - Fatal Execution Engine Error (7A09795E) (80131506)

Has anyone seen anything like this? Any suggestions on what to look at?

Answer 1

Nope not seeing this. I do lot of debugging of Classic ASP with VS2008 without problems like this. Apart from "Re-install stuff suggestion" I'm not sure what else you can do.

In the dim and distant past I've found debugging can be flakey when the process being debugged is running under reduced priviledged account but whether thats true now can't say. You might try as an experiment setting all the identites for the processes involved to the same as your interactive logon but I don't hold out much hope that that will help.

What O/S are you running?