Pesky little... breakpoint

[B00gyeMan]

Came to work today...
Fired up VS 2005... loaded the solution and attempted to reproduce a bug in a C# web app. Set some breakpoints, started IE, and went to pay a visit to that nasty page...

Surprise, for the breakpoints set in that code-behind page, VS 2005 says that "The breakpoint will not currently be hit. No symbols have been loaded for this document"

Cleaned the solution... nothing.
Cleaned the ASP.NET cache... nothing.
Cleaned the VSWebCache... nothing.
Re-installed the .NET 2.0 Framework... nothing.
Deleted all .pdb's... nothing.
Combinations of the above... guess what? Nothing...

The weird part is that I cannot debug that single page. Everything else is ok. All other pages. All other modules...

What the heck is wrong?

 

[chrissie1]

I think this is a wait for SP1 question/response. I have the same problem and an answer is nowhere to be found exept "live with it" It's like that pisky breakpoint that din't want to go away no matter how many times I clicked it.

Christiaan Baes
Belgium

"My new site" - Me

 

[B00gyeMan]

Ummm.. it worked until today... on that very same page... It's just that I had something else more important to do yesterday

 

[PGoRule]

Deleted all .pdb's...

I had the same problem, but still unable to find exact cause. We are using NANT build and attach the process to NUnit GUI. When this problem occurs we used to detach from process, clear the output folders, build it again, open a new instance, attach to process again...This works many a times.

Did the build generated .pdb's again?

Sharing the best from my side...

--Prashant--

 

[B00gyeMan]

Ok, someone is going to get his/her ass kicked really hard... Here's what happened: someone committed the .aspx file with the Page directive having debug="false" attribute...

Kicked really hard... literally...