You may suspect that there is logic behind that but the _MSV_VER value for cl.exe (cl.exe /?) in VS'2011 is 1700.
The old are:
MSVC++ 10.0 _MSC_VER = 1600
MSVC++ 9.0 _MSC_VER = 1500
MSVC++ 8.0 _MSC_VER = 1400
MSVC++ 7.1 _MSC_VER = 1310
MSVC++ 7.0 _MSC_VER = 1300
MSVC++ 6.0 _MSC_VER = 1200
MSVC++ 5.0 _MSC_VER = 1100
mardi 6 mars 2012
lundi 5 mars 2012
Today 5 AM, i was looking how i could easily migrate some old VS'2008 solution to the VS'11 Beta for testing.
The common upgrade method worked (devenv.exe /upgrade .sln) BUT.....
I used the several vsprop files a.k.a "Visual Studio Property Sheet" to store several properties relative to my computer. Include path to boost, and all the externals library, framework i used were in those files. But for them the upgrade result was a lit bit surprising.
For each .vsprop file i used, it create a new one call .prop. They was not empty, but they doesn't really contained what i expected. Both .vsprop and .prop are xml file but they have different syntax & schema.
It look like Visual Studio Dev Team didn't automatically translate the old format into the new.
But it can be easy to fix. As you can browse for those files through the VS Property editor and add all the include you need, all the specific setting you want and that per configuration. Save those file and if you share them across multiple solution, you do it only one times.
I missed the jump from VS'2008 to 2010 and that change is bit weird, but I suppose it lead to a better per project configuration instead of letting user using the old IDE VC++ folder configuration. It comes more easy to share project and 'build' configuration.
The common upgrade method worked (devenv.exe /upgrade .sln) BUT.....
I used the several vsprop files a.k.a "Visual Studio Property Sheet" to store several properties relative to my computer. Include path to boost, and all the externals library, framework i used were in those files. But for them the upgrade result was a lit bit surprising.
For each .vsprop file i used, it create a new one call .prop. They was not empty, but they doesn't really contained what i expected. Both .vsprop and .prop are xml file but they have different syntax & schema.
It look like Visual Studio Dev Team didn't automatically translate the old format into the new.
But it can be easy to fix. As you can browse for those files through the VS Property editor and add all the include you need, all the specific setting you want and that per configuration. Save those file and if you share them across multiple solution, you do it only one times.
I missed the jump from VS'2008 to 2010 and that change is bit weird, but I suppose it lead to a better per project configuration instead of letting user using the old IDE VC++ folder configuration. It comes more easy to share project and 'build' configuration.
jeudi 1 mars 2012
Hi,
A very powerful C++ toolkit i use a lot is Boost and when i started today my test of the new Visual Studio Beta, my first expectation was that Boost can be build with this new C++ compiler.
So i got a new copy of the Boost source code (zip package of the v1.49) and just follow the step describe here. And now i think that i get back tomorrow morning to check if every x86 and x64 binaries for msvc11 are ready.
Inscription à :
Articles
(
Atom
)