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?
For VSPackages, that means a user can have several Visual Studio versions installed on the same computer. However, you cannot have side-by-side versions of your VSPackages loaded into a single version of Visual Studio.
Visual Studio 2010 and earlier versions are no longer supported.
Starting from Visual Studio 2017, Community, professional and Enterprise editions can install side by side. The installation will not attempt to uninstall older versions and we don't need to uninstall older version of VS 2015/2017, before installing the VS2019.
Visual Studio 2012: support ends on January 10, 2023 for the IDE and its associated products, runtimes, and components. We recommend users upgrade to a newer version of Visual Studio. Visual Studio 2017: mainstream support ends April 12, 2022, and the product will transition to extended support until April 2027.
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).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With