I get this a lot on my franken-project. But it's a converted 1.0 -> 1.1 > 2.0 
webforms app.

First check that all assemblies are using the same framework. And you are in 
debug for all projects.

Then stop the project, clean all, rebuild all.  

If it still won't play. Stop, clean, delete a reference in the misbehaving 
project. Rebuild all. Click no to last build. Clean all, add the reference back 
in, rebuild all.

If it still won't work. Manually delete all bin and obj folders and try again.

I've learnt two things from my inherited fraken-project.

Rebuild all, doesn't.
Clean all, is a lazy bugger.

Davy.
-----Original Message-----
From: David Kean <[email protected]>
Sender: [email protected]
Date: Tue, 7 Dec 2010 07:25:51 
To: ozDotNet<[email protected]>
Reply-To: ozDotNet <[email protected]>
Subject: RE: The breakpoint will not currently be hit..nightmare!

Is the breakpoint a solid red circle once you've started debugging?

From: [email protected] [mailto:[email protected]] On 
Behalf Of Anthony
Sent: Monday, December 06, 2010 8:06 PM
To: 'ozDotNet'
Subject: The breakpoint will not currently be hit..nightmare!


Upgraded my asp.net  projects to VS2010 and now i can't debug my project as the 
breakpoints are not being hit.

*       I have deleted framework temporary files.

*       Delete bin and obj directories.

*       Re-referenced projects

*       According the modules window..the symbols are being loaded.


....still no luck

Anyone have suggestion....i'm going crazy!!!!

Anthony

Reply via email to