Debugging Woes (Part II)

T

Tyrant Mikey

New oddness in debugging ASP.NET Web applications.

(First off, I'm using VS.NET 2k3 to write an ASP.NET Web application in
Visual Basic .NET.)

I have a base class, which derives from System.Web.UI.WebForm. That
class contains a number of methods that I want to use on virtually all
of my pages. I have a break point set in one of the routines, named
ShowAlert().

When I run the application, the debugger stops on the next line in
ShowAlert after the breakpoint, with half of the line highlighted.
Analyzing the call stack shows that it is calling a different function
(ValidateAuthentication()) in the same file, but the line number
indicates that it's the line where my breakpoint is set, within the
ShowAlert method.

This has me completely baffled. It's the SECOND time I've run into this
today. Before today, I'd never seen it.

Any takers?

Thanks!!
 
A

Alvin Bruney [MVP]

take down the application, rebuild it. delete the pdb files. reboot and try
again. Your pdb files are out of sync with the executable code.
 
T

Tyrant Mikey

Thanks very much for the help.

Recreating the project file turned out to be less work than I expected
(I had forgotten all about the ability to create a blank project in an
existing folder). But recreating it worked.

Again, thanks much!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,743
Messages
2,569,478
Members
44,899
Latest member
RodneyMcAu

Latest Threads

Top