Getting to offending code from a stack trace

[murphy]

My release version of an asp.net has started throwing a
NullReferenceException. I get a stack trace in my browser that looks
like this:

[NullReferenceException: Object reference not set to an instance of an
object.]
QHOS.MUser.ResetUI(String curUserName) +143
QHOS.MUser.Page_Load(Object sender, EventArgs e) +72
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +744

In VS.NET it appears I need to be running a debug configuration in
order to see byte offsets in a disassembly view. Are these offsets the
same as they would be in a release configuration?

I'm assuming the byte offsets above are in decimal.

How does one get to the offending line from the info in the stack
trace?

And finally, was it not possible to put the name of the object in the
error message? ;-)

Thanks!

[murphy]

I ended up putting a debug version of the dll on the server with the
associated .pdb file. This allowed me to see the line number of the
exception. Based on the line number, I found that the offsets were
misleading when looking at the code in the disassembler. It could be I
was doing something wrong.