Ah. Yes of course, You've got a non standard build configuration.
Reset all the projects to build in their own. Bin/debug. Directories. Building into one directory is putting an old version with the same version number in there first before the new version is built. And if that is not the case, you need to recreate all your project files and solution file. The build dependance order is building in the wrong order. Davy. -----Original Message----- From: silky <[email protected]> Sender: [email protected] Date: Wed, 8 Dec 2010 17:12:41 To: ozDotNet<[email protected]> Reply-To: [email protected], ozDotNet <[email protected]> Subject: Re: The breakpoint will not currently be hit..nightmare!..solution? On Wed, Dec 8, 2010 at 5:09 PM, David Richards <[email protected]> wrote: > Anthony, > > Some years ago I was suddenly unable to debug ASP.Net solutions. I'm a bit > hazy on the details so I'm not sure if it was the same problem you are > having. After days of trying to figure it out, I ended up reverting my > machine (I work in VMs) to an old backup and I was magically able to debug > again. At the time, I attributed it to installing Chrome (when was it first > available for download?) since that was the only obvious difference in the > systems but who knows what the real cause was. The point is, it seems it > was an environmental issue. > > In other words, perhaps your planned rebuilding of your PC will solve the > problem. Looking at his earlier message it seems that the problem is the PDB has a different path then the file he's debugging on in VS. As to how that's happened, I don't know. I think the answer will lie in the article I posted though (or at least one of the links from it). > David > > "If we can hit that bullseye, the rest of the dominoes > will fall like a house of cards... checkmate!" > -Zapp Brannigan, Futurama -- silky http://dnoondt.wordpress.com/ "Every morning when I wake up, I experience an exquisite joy — the joy of being this signature."
