Why will the visual studio only lose its way by calling a function?


Apologies for the title, but I really am having difficulty even defining what's going on here.

I have a program with a line

long svnSuccess = SVNCommands.GetSVNHeadRevNo(svnLocation);

SVNCommands is a static class.

If I put a breakpoint on the line above, and then F11 (step into) to watch the execution of the code in SVNCommands it just... nothing. Behaviour is like an infinite loop. The program doesn't crash in any way. It just stops proceeding. VS doesn't take me to SVNCommands.GetHSVNHeadRevNo. I even have breakpoints at the start of that function (just to prove it's not getting there without realising) and they're not reached.

Any ideas as to what might be happening here?

Try adding System.Diagnostics.Debugger.Break() in GetSVNHeadRevNo and run the program without debugging. It should ask you if you want to debug and hopefully hit the code. Im not sure why your debugger isn't working. If SVNCommands was in an assembly that didn't match your debug file, it would give you a warning.

If that doesn't work, try deleting your Visual Studio Cache. To my understanding, that solves a lot of unexplained problems. Try using the answer from How do you clear your Visual Studio cache on Windows Vista?