Please help!!! VS.NET has lost the plot!

[steverbs]

Hi all.

Today, VS.NET's debugger has decided to go a bit mental. For some unkown reason, none of the breakpoints were hitting because of the dreaded Breakpoint will not currently be hit... symbols... etc" message. So, as this has happened several times before, I managed to fix it, by selecting the 'Generate Debugging Information' property under the project's properties. However, it is not entirely fixed as when the project begins to load, the damned breakpoint jumps on average 10 lines to rest in a different place than the one that I originally set. And also, while the project is running, it won't always let me set breakpoints where I want to and even more bizzarely, sometimes when I go to click to add a breakpoint at a certain place, it will add the breakpoint 5-10 lines below where I clicked!!!

Could somebody please help me? I'm an under alot of pressure with several projects atm and I've already wasted 3 hours trying to fix this infuriating problem!

Thank you in advance.

Stephen.

 

[ca8msm]

The dreaded VS curse!

I know it's not that helpul of a response but have you tried reinstalling as most of the time that works?!

----------------------------------------------------------------------

Need help finding an answer?

Try the search facility (

http://www.tek-tips.com/search.cfm)

or read FAQ222-2244 on how to get better results.

 

[steverbs]

That is what usually works for me as well, but I just don't have the time (or even the patience at this moment) to go through that whole 2 hour installation malarky.

 

[ThatRickGuy]

I can tell you exactly what is happening.

Some code you have changed did not get compiled. Wether you have the config manager set to not compile it, or that file had errors (and you clicked continue), or there is a cyclical references between to projects.

When this happens, the last compiled code is executed, but the new code is displayed by the IDE, so when the debugger hits line X, it will appear to be on line Y in the IDE. The code you are looking at is not what is running.

To correct this, make sure all of your projects are getting built correctly and that there are no cyclical reference (ie: project a references project b, which has a reference to project a)

-Rick

----------------------

http://www.ringdev.com

I believe in killer coding ninja monkeys.

 

[steverbs]

Cheers for the help. I had thought of the code not being compiled, so I edited and recompiled the project about 20 times tring to get rid of this problem and it compiled just fine every time. Also, there are only three projects in the solution (the key project, an ORMapper and a class library full of tool) and there are definitely no circular references. VS.NET doesn't allow them anyway.

 

[ThatRickGuy]

VS.NET doesn't allow them anyway

Oh but it does! Put a reference to project A in project B. Then in project A add a reference to the compiled Assembly of project B. Viola! Circular reference.

I've also seen this happen when people are working on multiple projects used in the same solution in different IDEs.

-Rick

----------------------

http://www.ringdev.com

I believe in killer coding ninja monkeys.

 

[steverbs]

Oh right! I hadn't thought of that. I allways use project references though, so I don't think that shoudl be a problem.

Stephen.