Publish not showing Line Number in production

[Chris Davoli]

When I get an error on my local machine (not try catch), I get the line # and
module it bombed in. This is what I need. After I publish and move to the
test server, it only gives me the error in hexadecimal format with no line
number or module that it bombed in. I'm moving the PDB file to the server
too. I publish with the toolbar Build, and then Publish web site. I check
"Allow the precompiled site to be updatable". Is there something else I need
to do to show the line number and module it bombed in instead of that funky
hex error message? How do I get the line number and module it bombed in?

--
Chris Davoli

[bruce barker \(sqlwork.com\)]

yes, use a debug build to get line numbers.

-- bruce (sqlwork.com)
"Chris Davoli" <Ch*********@discussions.microsoft.comwrote in message
news:EC**********************************@microsof t.com...

When I get an error on my local machine (not try catch), I get the line #
and
module it bombed in. This is what I need. After I publish and move to the
test server, it only gives me the error in hexadecimal format with no line
number or module that it bombed in. I'm moving the PDB file to the server
too. I publish with the toolbar Build, and then Publish web site. I check
"Allow the precompiled site to be updatable". Is there something else I
need
to do to show the line number and module it bombed in instead of that
funky
hex error message? How do I get the line number and module it bombed in?

--
Chris Davoli

[Chris Davoli]

This is VS2005
Thanks, but where do I do the debug build? the only three choices it gives
me when i publish is
"Allow the precompiled site to be updatable"
"use fixed nameing and single page assemblies"
"Enable strong naming on precompiled assemblies"

Where do I specify this?
--
Chris Davoli

"bruce barker (sqlwork.com)" wrote:

yes, use a debug build to get line numbers.

-- bruce (sqlwork.com)
"Chris Davoli" <Ch*********@discussions.microsoft.comwrote in message
news:EC**********************************@microsof t.com...

When I get an error on my local machine (not try catch), I get the line #
and
module it bombed in. This is what I need. After I publish and move to the
test server, it only gives me the error in hexadecimal format with no line
number or module that it bombed in. I'm moving the PDB file to the server
too. I publish with the toolbar Build, and then Publish web site. I check
"Allow the precompiled site to be updatable". Is there something else I
need
to do to show the line number and module it bombed in instead of that
funky
hex error message? How do I get the line number and module it bombed in?

--
Chris Davoli

[Juan T. Llibre]

In web.config : <compilation debug = "true|false">

Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Chris Davoli" <Ch*********@discussions.microsoft.comwrote in message
news:3C**********************************@microsof t.com...

This is VS2005
Thanks, but where do I do the debug build? the only three choices it gives
me when i publish is
"Allow the precompiled site to be updatable"
"use fixed nameing and single page assemblies"
"Enable strong naming on precompiled assemblies"

Where do I specify this?
--
Chris Davoli

"bruce barker (sqlwork.com)" wrote:

>yes, use a debug build to get line numbers.

-- bruce (sqlwork.com)
"Chris Davoli" <Ch*********@discussions.microsoft.comwrote in message
news:EC**********************************@microso ft.com...

When I get an error on my local machine (not try catch), I get the line #
and
module it bombed in. This is what I need. After I publish and move to the
test server, it only gives me the error in hexadecimal format with no line
number or module that it bombed in. I'm moving the PDB file to the server
too. I publish with the toolbar Build, and then Publish web site. I check
"Allow the precompiled site to be updatable". Is there something else I
need
to do to show the line number and module it bombed in instead of that
funky
hex error message? How do I get the line number and module it bombed in?

--
Chris Davoli