The last contract I worked on they were using Visual Studio 2013. I'm personally using 2015 for my project. I chose to upgrade because it fully supported C++ 11, which I make heavy use of. I will likely upgrade to Visual Studio 2017 to take advantage of the C++ 14/17 features they've implemented, though I plan to wait until they have a few patches or possibly even service pack 1. When you're working on a game with real deadlines, you can't take a chance on a brand new compiler unless absolutely necessary.

Having never used VS 2017, I can't comment on how Game Coding Complete handles it. The hardest part, as always, will be getting the 3rd party libs to compile.

-Rez

You mean just build with the old compiler? You could, but then you wouldn't be using the new compiler. You'd be using the new IDE, sure, but you would miss out on the most important benefits of the upgrade.

-Rez

rezination wrote:

Having never used VS 2017, I can't comment on how Game Coding Complete handles it. The hardest part, as always, will be getting the 3rd party libs to compile.

-Rez

I have it up and running on VS2017. If there's interest, I can upload the code to GitHub and the libs to Dropbox.

Gaddam wrote:

That would be awesome!

I uploaded the code to a branch in my GitHub repo.

The updated libraries are available at this Dropbox URL.

georgerbr wrote:

Gaddam wrote:

That would be awesome!

I uploaded the code to a branch in my GitHub repo.

The updated libraries are available at this Dropbox URL.

I just checked your commit, other than changing comments, any actual differences? It should just work from origin master right? Any problems with libs compilation?

Wolkec wrote:

I just checked your commit, other than changing comments, any actual differences? It should just work from origin master right? Any problems with libs compilation?

The solutions were retargeted, and the name of the GameCode4 lib output file was changed. The EditorAppDLL also outputs a DLL with a different name.
No, because of the changed GameCode4 lib name. Also the EditorApp now takes another DLL name.
Effects11 needed a bit of work. All other libs built right out of the box.

Just tried running it, how did you get it to work, i can't seem to get the dx utils to work, I'm using the dx that comes with windows 10 sdk. Did you use jun 2010 ver?

fatal error C1083: Cannot open include file: 'dxsdkver.h': No such file or directory
etc

Wolkec wrote:

Just tried running it, how did you get it to work, i can't seem to get the dx utils to work, I'm using the dx that comes with windows 10 sdk. Did you use jun 2010 ver?

fatal error C1083: Cannot open include file: 'dxsdkver.h': No such file or directory
etc

Yes, I used the June 2010 DirectX SDK. All the instructions in the README, except for the 3rd party libs, still apply. Same versions of everything, bugs and all.

I just installed 2017 myself, so I can take a crack at this, and get an update pushed to the repository.

Any news on this?

bbmario wrote:

Any news on this?

Did you run into any issues with the code and libs I posted back in April of last year?

I got this to work with VS 2022 Community. I had to add some library links and links to the the Direct X June 2010 SDK.

So, the VS2017 version that was posted still works.

Does this use Direct X 9? Seems like it. I have not read through the book yet.