When the dll is built, it keeps record in the .dll of the file locations
used to create the dll. If you do not want to see this, you will need to
turn off custom errors tag in the web.config file. It should be defaulted
RemoteOnly which means you only see the stack trace when on the machine
itself.
The pdb file has all the debugging symbols. It is showing you actual source
code, or just the stack trace where the exception occurred.
You deployed it correctly, but if you are moving to your production server
with your code, you should switch over to Release mode before building your
solution and change the compiliation tag in your web.config. The Release
dll code will run slightly faster than your debug mode code.
bill
"Vishal" <an*******@discussions.microsoft.com> wrote in message
news:19****************************@phx.gbl...
Yes, I used debug mode. I selected "copy only required
files to run the application". I dunno if it has deployed
the pdf file or not. What I am supposed to do?
-----Original Message-----
Did you build your soltuion in debug mode before
releasing your site? Didyou include the .pdb file when you deployed?
Don't.
bill
"Vishal" <an*******@discussions.microsoft.com> wrote in
messagenews:03****************************@phx.gbl... Hello,
I have uploaded my website from VS to my server and
unfortunaly there is an error when I visit the website.
However the stack trace of the error still points to my
local directory. It says something like this:
NNTP.readpost.BindData() in E:\NNTP\default.aspx.vb:44
NNTP.readpost.Page_Load(Object sender, EventArgs e) in E:\NNTP\default.aspx.vb:34
Why is this still pointing to my local path?
.
