I kind of forgot about this question, until today a friend said how big C ++ 0x is. I still love VS2008, much more than since 2010, which is primarily slow, so I decided to let it go. And I still can't believe it, but with a minimal amount of hacks it really works.
And it works great: sitting in front of VS2008, you don’t even notice it with the 2010 toolkit. If you do not look at the cl / link logo. Or, of course, if you suddenly cannot use lambda. So far, I could not find any problems. Editing, etc. It works the same way it was done, construction work, debugging work, everything I need.
Here is what I did:
- , Windows SDK 7.1/VS2010, devenv VS2008. 2010 setenv.cmd.
- : msobj100.dll, mspdb100.dll, mspdbcore.dll mspdbsrv.exe VSINSTALLDIR/bin 2010 ( PATH somweher). , cl.exe .
- ,
devenv /useenv
x64:
SET PlatformToolset=Windows7.1SDK
SET ToolsVersion=4.0
SET WindowsSDKVersionOverride=v7.1
SET Path32=%ProgramFiles(x86)%
SET "VCINSTALLDIR=%Path32%\Microsoft Visual Studio 10.0\VC\"
SET "VSINSTALLDIR=%Path32%\Microsoft Visual Studio 10.0\"
SET "VCTools=%VCINSTALLDIR%Bin"
SET "VCTools=%VCTools%;%VCTools%\VCPackages;"
SET "VCLibraries=%VCINSTALLDIR%Lib"
SET "VCIncludes=%VCINSTALLDIR%INCLUDE"
SET Path=%FxTools%;%VSTools%;%VCTools%;%SdkTools%;%Path%
SET OSLibraries=%WindowsSdkDir%Lib
SET OSIncludes=%WindowsSdkDir%INCLUDE;%WindowsSdkDir%INCLUDE\gl
SET "LIB=%VCLibraries%;%OSLibraries%;%FxTools%"
SET "LIBPATH=%FxTools%;%VCLibraries%"
SET "INCLUDE=%VCIncludes%;%OSIncludes%"
EDIT batchfile /useenv, , , : V++- % APPDATA%/VisualStudio/9.0/VCComponents.dat. , $(VCINSTALLDIR) $(ProgramFiles)\Microsoft Visual Studio 10.0\VC \, .