Abnormal Program Termination when executed from C:\Program Files\...

This is a discussion on Abnormal Program Termination when executed from C:\Program Files\... within the Windows Programming forums, part of the Platform Specific Boards category; Originally Posted by Salem
I prefer this - http://www.microsoft.com/whdc/devtoo...g/default.mspx
You can run and debug the program wherever it is, and ...

Visual Studio also contains a very powerful, and if not easier, debugger.
You can get it for free at http://www.microsoft.com/Express/.
But you should try out for yourself if it's to your liking. No sense in using something that you don't like.

Yes, you would have to installing the IDE, then compile your source.
I'm not sure if or how you can debug apps with windbg with source code information. I'm not sure how that works and what compilers can produce the correct debug information...

The debugger inside Visual Studio doesn't really require you to compile with the Visual C++ compiler per se... just as windbg, it works fine by attaching to executables.
However, I know the VS debugger requires program database files (aka debug files) for being able to properly debug (or you'll just get assembly output). Maybe this can be generated from other compilers too, but I don't know for sure.
Otherwise, VS is not a bad idea and VC++ is not a bad compiler, if you have the option to switch and try it out.

"Do the port"? I don't understand what you mean by that, but...
You do realize that standards compliant code will compile in any compliant compiler, yes?
Anyway, I'm going to trust you have your reasons. Unfortunately, the rest of how to make it work is beyond my knowledge.

Well isn't that just more or less their version of MFC? I am not qualified to answer that question on my own since I do not have a PhD in proprietary useless libraries. Which also means I am not welcome to work at Microsoft. Its listed as one of their basic requirements.

Make sure that the account your application is running under can write to %ProgramFiles%, because normally, an application SHOULD NOT write to it's install directory. %ProgramFiles% could be write protected in your execution environment.

Use SHGetFolderPath to find a folder suitable for writing data. APPDATA or LOCAL_APPDATA comes to mind.