• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
n00by2077

Have Solution/Project for both VS2010/2012

8 posts in this topic

If you want to make a Solution and Project, for both VS2010 and VS2012, what things you have to change for all to work out without problems? 

My guess:

 

1. Solution_vs2010.sln with Project_vs2010.vcxproj

2. Rename Solution_vs2010.sln to Solution_vs2012.sln

3. Rename Project_vs2010.vcxproj to Project_vs2012.vcxproj

4. Edit  Solution_vs2012.sln and change inside Project_vs2010.vcxproj to Project_vs2012.vcxproj

5. Open Solution_vs2012.sln with VS2012 and let it make conversion

 

Still there must be something more to change because after opening the converted VS2012 solution/project, there is no code files added like in the 2010 project.

 

Thanks

0

Share this post


Link to post
Share on other sites

You change nothing, that was one of the major changes from VS2010 to VS2012. If your project was based on VS2010 you could have part of your team work in VS2010 and part of your team work in VS2012. If you start a Windows 8 / WP8 project in VS2012 (can only do metro in 2012 anyway) you can't work in 2010 with it.

1

Share this post


Link to post
Share on other sites

Missed responding to your last statement, the VS2012 interface is slightly different so you need to set things up to show the proper solution explorer and property pages, I currently have one machine that has VS2010 and another that has VS2012 and work on the same projects dpending on whether I at home or away and have no issues.

0

Share this post


Link to post
Share on other sites

But after opening the project in 2012 I can't compile it in 2010 because it changes the compiler toolkit version used:

 

 

Configuration 'Debug|Win32': changing Platform Toolset to 'v110' (was 'v100').
Configuration 'Release|Win32': changing Platform Toolset to 'v110' (was 'v100').

0

Share this post


Link to post
Share on other sites

If you require people to use different toolsets for working on your code base I would suggest using a utility like CMAKE or Premake to generate the solution/projects. This way you distribute the CMAKE or Premake files and people can have those build the VS/make/XCode projects that are required for what you are working on.

 

I modified the premake source a little while back in order to make it work with VS2012. I can probably post it online later today if you consider that as an option.

Edited by CornyKorn
1

Share this post


Link to post
Share on other sites

Can't be made some kind of if-condition inside project files that choose between v100 and v110 toolset if its opened by vs2010 or vs2012? 

 

I'm not familiarized with CMAKE or Premake, so I don't know, but would be nice to have a look to this solution and see how it works, thanks :)

0

Share this post


Link to post
Share on other sites
I'd hate to be using VS2012 and having to forgo all the good stuff added to it.

On the other hand, if you really must stay VS2010 compatible, then is it a big deal to standardize on everyone using VS2010? Edited by Stroppy Katamari
0

Share this post


Link to post
Share on other sites

I've not used 2012, but if I want to open a vs2008 solution in my vs2010 then I just open it... Visual Studio does the conversion automatically? Doesn't 2012 not do this?

0

Share this post


Link to post
Share on other sites

I'd hate to be using VS2012 and having to forgo all the good stuff added to it.

On the other hand, if you really must stay VS2010 compatible, then is it a big deal to standardize on everyone using VS2010?

 

Its useful to open the project, in VS2010 or VS2012, and not need to do anything to be able to compile it, I have tested and when opened in 2012 it changes the compiler toolset version used, then if you come back and open it in VS2010 you can't compile without editing the .vcxproj file.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0