Getting line number in Exception for ASP.NET | Tech Off

JParrish

Hoping someone may have overcome this before.

I use the enterprise library exception handling block to email myself any errors that occur within my ASP.NET application. At one time, I was getting the line numbers of the exceptions. I realize the performance hit but it is ok while I am testing deployment in new environments. Lately I have not been able to get the line numbers any more which makes the error too ambiguous. I have my build configurations to active debug, and in the web.config compilation debug is true.

For libraries I call from the web app, I have the pdb files deployed into the bin folder. Does anyone know anything more I can check/do to try and get the exception to include the line number? I am using fixed name single page assemblies if that matters.

ScanIAm
On a scale of 1 to 10, people are stupid.

JParrish wrote:

Hoping someone may have overcome this before.

I use the enterprise library exception handling block to email myself any errors that occur within my ASP.NET application. At one time, I was getting the line numbers of the exceptions. I realize the performance hit but it is ok while I am testing deployment in new environments. Lately I have not been able to get the line numbers any more which makes the error too ambiguous. I have my build configurations to active debug, and in the web.config compilation debug is true.

For libraries I call from the web app, I have the pdb files deployed into the bin folder. Does anyone know anything more I can check/do to try and get the exception to include the line number? I am using fixed name single page assemblies if that matters.

I'm not familiar with how to set this up for web remote deployments, but if you have control over what shows up in the email, then look at

System.Exception.StackTrace

it's part of the exception object, and it should hold the stack trace and line numbers (if they are available).

JParrish

ScanIAm wrote:

I'm not familiar with how to set this up for web remote deployments, but if you have control over what shows up in the email, then look at

System.Exception.StackTrace

it's part of the exception object, and it should hold the stack trace and line numbers (if they are available).

Thanks.. but yes the template formatting the email includes the full stack trace, which would contain the line number. That is the part I don't understand, it should show me the line number since it was compiled for debug and symbols for other libraries are there. Expressionless