When the game programming, the debugger is very difficult, especially full screen mode, can't switch to the IDE environment of VC. I usually use Bltfast instead of flip to ensure that GDI Surface is always before, but the effect is not too good, I found a baby in the VC, I can use two computer debugging programs, one running program, and another running VC to debug, plus trace output, really cool, the following is my approach:
1. Guarantee that the two computers are networked, it is best to be in front of you, otherwise you must run away. Also guarantees that your program can run normally on both computers, such as DX8 installed.
2. Suppose you use A machine to run VC to program and debug, run your program with B machine, if the B machine does not install VC, you need to copy the VC's debug monitor to the B machine, the specific file is MSVCMon.exe, MSVCRT.DLL, TLN0T.DLL, DM.DLL, MSVCP6O.DLL and MSDIS110.DLL, if the B machine is running NT, copy file PSAPI.dll. These files in the CommON / MSDEV98 / BIN directory and system directory in the VC installation directory.
3. Create a shared directory on the B machine, be sure to set it fully to ensure that the A can write files on B at any time.
4. Open your program project file on A, Alt F7 Open Project Setting, select the Debug page, fill in the file path and name on the B machine in Excutable for Debug Session and Remote Executable Path and Name, such as the IP of the B machine The address is 172.16.4.60, the shared directory is named Debug, the project is TEST, then //172.16.4.60//Debug/test.exe, also fill in the same content in the Output File Name of the Link page. Then select the menu build-> Debugger Remote Connection, and fill in the IP address of the B machine in Setting.
5. Run MSVCMon.exe on the B machine, press Connect Waiting to wait, and then start the debugger on A, if your program is running on B, if you have any questions, please refer to the debugging remote Applications in MSDN .
