I had a similar problem in the past:

Suddenly, my code started executing wrongly, so I started step by step debugging of the offending routine (which before worked perfectly ).

The strange thing is that the step by step debugging (pressing F8), just jumps over two lines of code. They are non executed, and the highlighted yellow bar just jumps to the third line.

It does similar things when the code is not compiled, and the debugger runs an older compiled executable, so the compiled code does not match the code.

This started one day in which a non graphic class started to no more being displayed, and instead appeared the same message that appears when a form is wrongly hand-edited, and cannot be displayed.

I had a similar problem in the past, and it was solved by deleting a file, but I don’t remember what file, and cannot recover the post (not even the forum), in which I was advised to delete the file.

I deleted the entire bin directory, and rebuild the entire solution, but it does not works.

Somebody can give me a clue?

I are running visual Studio 2008, in windows 7 64 bit, compiling for Any CPU.