Visual Studio maintains a list of locations to look for library source files
when you are debuging. If this information gets corrupted or you press cancel to one of the dialogs
asking where source code is, you won't be able to step into MFC code.

You can view/edit the locations by right clicking on your solution, selecting properties and then "Debug Source Files". I think either deleting all the entries here or setting them to the correct values should
do the trick.

If say in my code I have the following function call:
CString S;
MyFunction(S);

If when I'm on the MyFunction line in the debugger and I hit F11 (step into), I just want to step into my code. But this is not what is happening - it goes into the disassembly... Very annoying. I just want to disable the disassembly stuff.........

My work around is to use "Step Over" (F10 on my computer) as my default "single step" then when I get to a function that I want to step into, I use the other key.
Also, if you acccidently step into ASM code, just hit "step out of" (Shift+F11) and Robert's your papa's brother.

Your work around was my work around too.... I just hate having to even see ASM code and doing the shift-F11 every time to get out of it - because even when I do that, I have to right-click and say 'view source code' - to see a normal code listing again........

Introduction:
Dialogs (1) modal - maintaining the database.
Continuing from the ninth article about sudoku.
You might have heard of modal and modeless dialogs. Here with this Sudoku application will we use one of each type: a modal dialog …

For those of you who don't follow the news, or just happen to live under rocks, Microsoft Research released a beta SDK (http://www.microsoft.com/en-us/download/details.aspx?id=27876) for the Xbox 360 Kinect. If you don't know what a Kinect is (http:…