missing line numbers in stacktrace when precompiling

microsoft.public.dotnet.framework

2 Mar 2006 12:17 PM

Kieran Toon

I'm using Visual Studio 2005 and have an ASP.NET web application written in
Visual Basic.
When the application runs on my local webserver and hits an error, my
errorhandler writes out debug information using the Stacktrace method of the
exception object.

However the line number of the exception and the file where it occured does
not display when I deploy the application to the live server using either
the following command:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_compiler -v
"\internal\hris" -p "C:\Inetpub\wwwroot\internal\HRIS" -u -d -f -c
"J:\Inetpub\wwwroot\internal\HRIS"

where J: is the mapped drive to the live webserver. I'm careful here to
specify "-d" to include debugging information, "-c" rebuilds from scratch
etc... Indeed the .PDB files required for debugging appear in the bin
folder of the web application. What is going on?

If I simply copy the files from my local webserver to the live server (IIS
forces me to then delete the App_data and App_code), this includes the .vb
code-behind files, the line numbers appear.
How do I get the line numbers to appear without having the .vb source
code-behind files on my live web-server? All the documentation seems to
imply it is possilble.

Many thanks,
Kieran Toon

The examples:

Without line number info:
STACKTRACE: at HRIS.ConfirmUpdate.Page_Load(Object sender, EventArgs e) at
System.Web.UI.Control.OnLoad(EventArgs e) at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)

With line number info:
STACKTRACE: at HRIS.ConfirmUpdate.Page_Load(Object sender, EventArgs e) in
d:\inetpub\wwwroot\internal\hristest\Secure\ConfirmUpdate.aspx.vb:line 72 at
System.Web.UI.Control.OnLoad(EventArgs e) at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)