If possible at all, does anyone know how to use the full c++ toolset shipped with Visual Studio 2010 (compiler/linker/sdk) in Visual Studio 2008?
Would changing all directories listen under Options->Projects and Solutions->VC++ Directories be sufficient, or is there more to it? And suppose I try it this way, are there any caveats to it?
相关问题
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- the application was unable to start correctly 0xc0
- Visual Studio 2019 - error MSB8020: The build tool
- 'System.Threading.ThreadAbortException' in
相关文章
- How to show location of errors, references to memb
- Log4Net Multiple Projects
- How to add external file to application files ( cl
- How to track MongoDB requests from a console appli
- Compiling error in C++ project with C and C++ code
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- VSIX: execute code on VS startup
I kinda forgot about this question until today a friend was saying how great C++0x was. I'm still in love with VS2008, much more than with 2010 which is above all things slow, so decided to give it a go. And, I still can't believe it, but with a minimum of hacks it actually works.
And it works great: sitting before VS2008 you don't even notice it's actually using the 2010 toolset. Unless you look at cl/link's logo. Or off course, unless you are suddenly able to use lambdas. I could not find any problems so far whatsoever. Editing etc works like it alwasy did, building works, debugging works, that's all I need.
Here's what I did:
devenv /useenv
This is the used batchfile for an x64 machine:
EDIT instead of batchfile combined with /useenv, there's another way that does the same but more direct: the settings for VC++ Directories are all saved in the file %APPDATA%/VisualStudio/9.0/VCComponents.dat. So if you take the original one and replace all occurrences of $(VCINSTALLDIR) with $(ProgramFiles)\Microsoft Visual Studio 10.0\VC\ it works as well.