I would like CB to be 100% portable, i.e that it really avoided to save any config files to C:/.
Recently I had to reinstall the OS, and since I forgot CB was storing a lot of config files to C:/Users/Name/AppData/Roaming/Codeblocks, I also forgot to backup that folder, and I had a very bad day since I lost all my CB settings, compiler settings, colors, everything. It should really store all its settings within its program folder. Thanks
I second that. Except for minor things like desktop shortcuts, uninstaller entries and maybe a few other cases I prefer programs and their configuration to be fully contained within their installation folder. There is, of course, the issue of the "Program files" folder requiring administrator privileges to alter anything within, meaning Code::Blocks would have to be launched in elevated mode. But I personally keep all my installed software on a separate partition, so this is not much of a problem. I suggest checking the installation folder, either via installer or by Code::Blocks itself, and write configuration files to the default location if Code::Blocks is installed in the "Program files" directory, or within the directory of Code::Blocks itself if it is deployed elsewhere.
Thanks T-640. Imho installing programs to C:/ is a very bad practice (despite Windows tries to force you to do so) and for a lot of reasons, in fact I install all programs in a separate D partition.
If you need a portable version of Code::Blocks, you can download C::B nosetup.zip.