n00by2077

Right, but something recommended by own experience, or because is very good ?

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.

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

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').

Thanks to your replies and different opinions, I am going to try some of them, the perforce, git and mercurial, but as I saw in git webpage, that is very well done and explained, with a simple tutorial and a free book, I think that at the end will choose it, but anyway I'm going to try them all and see which one feels better for one-person programming.