views:

232

answers:

3

Web config has debug=true and the project is a debug build and the pdb files are present in the bin directory, but I do not get line numbers in my stacktrace when an exception is thrown.

Works fine with local IIS/Cassini but not on our test IIS servers. Is there some obvious setting that I might be missing?

+1  A: 

Check the MAchine.Config file

In ASP.NET 2.0 there is a switch that can be turned on in machine.config that turns off all debug=true, so in 2.0 applications you can do this directly without worrying about finding out which applications do and don’t have it.

<system.web>

      <deployment retail=”true”/>

</system.web>

Sources from http://blogs.msdn.com/tess/archive/2006/04/13/575364.aspx

rangitatanz
I tried this on the local machine and it actually completely turns off the trace - only the exception text is returned. With the default I get the trace, just no file names and line numbers present.
Graeme
A: 

It turns out using impersonation with the web.config:

<identity impersonate="true" />

causes the loss of the line numbers in the stacktrace. I took the entry out and my line numbers returned, put it back and after a few hours (Kerberos ticket refreshing?) the line numbers disappeared again.

Not sure why impersonation affects the stack trace but it does - would be happy to have someone confirm / explain this...

Graeme
Someone else noticed it in 2nd last post of this thread, but no explanation given:http://channel9.msdn.com/forums/TechOff/257195-Getting-line-number-in-Exception-for-ASPNET/
Graeme