upgrade Nebula3 vs project version to vs2010

Nebula3’s official blog has updated for one entire year! No news is good news, now, I decide to get my hand dirty.

I have spend almost one month to get a general knowledge of the engine’s appearance. Thanks to xoyojank for your articles and help.

Now, I think it’s the time to get deeper and find more intrinsic problems.

I found vs2010 support a better intelligence feature, which can be helpful for comprehending the source hierarchy. The last Nebula3 version only has vs2008 project files, which are configured and auto-generated by a set of tcl scripted. unfortunately, I know little about tcl script language. At last, I decide to upgrade some core project and solution files to vs2010, even though I know it’s a burden when re-configuration happens.

The Steps:

1. copy folder vs9.0 to vs10.0 which share the same parent directory with vs9.0.

2. open tool_win32.sln in vs10, and let vs10 upgrade the project file automatically.

3. fix some bugs which are brought as upgrading

    3.1 use Ctrl+X and Ctrl+V to correct some cpp files’ character set.

    3.2 as shfolder.h has been deprecated in vs2010, use shlobj.h instead, and use NOCTLMGR macro now.

    3.3 as a consequence, CreateDialog in dialogmanager.h is been translated into a macro which defines inside of the CTLMGR. the solution is to use #undef CreateDialog to disable this macro.

4. add $(DX_DIR)include and $(DX_DIR)lib\x86 in VC++ directory.

5. modify "Output Directory", "Target Name" so they are the same path and target as the one specified in Output File.

FIXME: the standard way to modify the solution and project configuration is editing "makeslnwin32.tcl" located in the bin directory, then use tool to generate solution files automatically.

now, when the projects switch between "Debug" and "Release" configuration, we should manually clean the solution before build the solution, otherwise, libs generated under different  configuration previously will conflict with each other.