Reputation: 13511
I know traditionally its best to install programs in the order they were 'born' as that's generally going to avoid more problems.
Are there any known chronological dependencies between these two programs?
Upvotes: 28
Views: 15322
Reputation: 48267
It works on my machine.
I just did it a day or so ago and had no problems. I was surprised at how smoothly it went, so if that's any indication of the usual, it should be a breeze.
Visual Studio is pretty good about installing to a particular directory, with the exception of support components (which are detected as already-installed and skipped). When installing 10 after 11, only 10 itself and a runtime or two were needed. Both 10 and 11 have been working perfectly since, including 11's support for compiling projects as 10 (to support XP, which was why I installed both).
It does get a little bit messier with installing 9 (2008), but you can typically install that after 10 and use the back-compiling. I have no idea what happens if you install 11, then 10, then 9 (it could work).
Upvotes: 21
Reputation: 39380
VS 2012 broke 2010 for me, but I don't know if it would break the other way. Certainly, don't do it on your production environment.
Workaround : freely downloadable Windows SDK has the vc10 compilers and toolchain, and you can use it when compiling from VS2012. Just select appriopriate platform toolset in project options.
Upvotes: 0