[Stormkeeper]

I've been using VS 08 in school, so I wanna know if its compatible with 08. The source code I mean. Is there a 08 build, or do I have to do the conversion myself ?

[Wanderer]

Just use the MSVC2005 project... It should be able to make use of that - well at least mine is. Though remember that if you have only the Express Edition you are not able to compile Fred builds, only actual game builds (MFC issue).

[Stormkeeper]

It forces me to convert.

[Wanderer]

Then let it

[Stormkeeper]

Yea, I did.

[Wanderer]

So did you get it to compile?

[Stormkeeper]

Only warnings.

Seems to compile fine otherwise.

[chief1983]

Fred too?  If I remember I had to make a couple edits to a file to get Fred compiling to work.  Also, since I had it set up with Tortoise I just created a copy of the MSVC 2005 directory called MSVC 2008 or whatever, and let VS convert that instead.

[Stormkeeper]

Fred too?  If I remember I had to make a couple edits to a file to get Fred compiling to work.  Also, since I had it set up with Tortoise I just created a copy of the MSVC 2005 directory called MSVC 2008 or whatever, and let VS convert that instead.

Iirc, I think Fred compiled fine. Is the folder in the svn ?

[chief1983]

Yeah, but on one of the configs it doesn't build by default, at least not for me after conversion.  I have to manually compile FRED every time for some reason, even when just hitting build solution.

[Stormkeeper]

Strange. I don't get that. I'll check when I get back on my laptop.

=edit=

Yea, it doesn't build by default.

Also, building the stock build results in errors.

[phreak]

I'm getting VS2008 free through school via the MSDNAA.  I should have the vs2008 project files ready to go hopefully by the end of the weekend.

[chief1983]

And in SVN?  That'd be nice, then I might be able to use those and figure out why my builds don't read from the registry on Vista the same as everyone else's.

[phreak]

probably because of this

This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project.

By default, the Visual C++ linker embeds a UAC fragment into the manifest of an application with an execution level of asInvoker. If your application requires administrative privileges to run correctly (for example, if it modifies the HKLM node of the registry or if it writes to protected areas of the disk, such as the Windows directory), you must modify your application.

The first option is to modify the UAC fragment of the manifest to change the execution level to requireAdministrator. The application will then prompt the user for administrative credentials before it runs. For information about how to do this, see /MANIFESTUAC (Embeds UAC information in manifest).

The second option is to not embed a UAC fragment into the manifest by specifying the /MANIFESTUAC:NO linker option. In this case, your application will run virtualized. Any changes you make to the registry or to the file system will not persist after your application has ended.

The fix is to change the launcher and FS2 to read from HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE in the registry.

[phreak]

committed.  I also added multi-processor compiling for the release builds, it takes about 90 seconds to compile the whole codebase now on my quad extreme. (instead of something like 5 minutes).

[chief1983]

Awesome, that even eliminated the need for those changes to some of the FRED code to make it compile.  I figured that was what needed to be done for Vista, my only concern was that my builds specifically seemed to be the ones that showed any trouble at all.  Wasn't sure what settings others were using that were getting around that.

[phreak]

Updated project files to include additional compiler optimizations.  I also added two additional release configurations for SSE/SSE2 builds.