VS2008 single stepping.

[ASB]

Often doesn't

I have moved a load of things to VS2008 and done a debug build. Problem is when single stepping it often decides to simply run instead. I can't figure out the catalyst for this at all despite extensive searching.

Anybody else had any similar issues. It's a bit of a bugger to say the least, set the breakpoint, stops. Press F11 and off it goes into run mode instead.

[DimPrawn]

Never had that problem. Ive had the source code out of sync with the debug file and it stepping into whitespace and skipping lines.

[Weltchy]

You dont have the debug step over attributes decorating your class / methods do you?

Also, if you've referenced the build dll in the gac but the project your running against has a different version, sometimes this will cause the code to not step in.

Also, if your making calls into a WCF service, then depending on the setup of your endpoints, this might be an issue.

[Weltchy]

And of course, the issue could be that the single step function is assigned to another key. I grew up with VB, hence I choose the VB Keyboard layout which uses F8 as the single step key.

[Jaws]

Are you certain the code being called resides in a debug build of an assembly? It may be worth checking this or checking the references in your project to ensure they are mapped to either another project in your solution or the debug version .dll.

[VectraMan]

Not had that, but I've often had the goes away for 30 seconds and locks up the entire machine. Maybe it's doing that and you just think it must be running?

[ASB]

Thanks for all your usuful ideas. But:-

- It doesn't happen all the time. Different runs of the same code with the same breakpoints behave differently

- The main process was running in a host and this doesn't die when the debugging is ended. Unchecking this seems to have stabilised things a bit [but not entirely]

- There is no WCF involved

- None of my code is in the GAC

- I have cleaned absolutely everything and only done a debug build just in case

- It only ever seems to happen when invoking code across an assembly boundary

- Swearing at it hasn't helped.

But thanks for trying.

[Churchill]

Select "view as Assembly" and single step the assembler instructions, that should give you a pointer(pardon the pun) to where the problem lies.

[NickFitz]

- It doesn't happen all the time. Different runs of the same code with the same breakpoints behave differently

I thought Windows was always like that?

[ASB]

I thought Windows was always like that?

But so true..