views:

159

answers:

2

I'm getting a crash while trying to debug a asp .net application via webdev from Visual Studio 2008. Normally, the usual way of troubleshooting this issue is to narrow down the code change that would lead to the crash. This is usually time consuming. Fortunately, this only happens once in a blue moon.

I'm wondering if there is a faster way of troubleshooting these kind of crashes. Failing that, what are the usual causes that would cause webdev to crash?

Update:

  • My current case seems to be caused by a stack overflow. :)
+1  A: 

Are you able to get an exception message being thrown? If not, I'd recommend downloading and injecting ELMAH (a nice debugging tool) into your app to see what is going on at crash time.

Dillie-O
+1 - ELMAH looks quite cool, I have a similar widget, but this looks much more comprehensive.
Kev
Yes ELMAH is cool. I use that as well but no exception is thrown in Visual Studio when the webdev crashes. Haven't you encountered a scenario like that?
seanlinmt
I never use the VS development server other than for trivial knock-about stuff to prove an idea in VS Express.
Kev
I've never had anything where the Visual Studio dev server crashed as as result of code. One other thing you might try is to run the Debug View program by SysInternals. If the Dev Web Server is outputting some crash code to StdOut, it'll pick it up. http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
Dillie-O
A: 

You might be able to use ADPlus to find out why the VS web server is falling over:

How to use ADPlus to troubleshoot "hangs" and "crashes" (MS KB286350)

Tess Ferrandez's site has loads of good stuff about using ADPlus and WinDBG for these kinds of gnarly problems:

If broken it is, fix it you should (Tess Ferrandez, ASP.NET Escalation Engineer (Microsoft))

Kev