The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Most college students will only use Word, Excel, a web browser, and Fortnight.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
Where I've heard problems can occur is not so much the installations, but updates to the earlier installed version. (Also, not applicable for you but in general the higher version needs to be installed before the lower - i.e. 2019 after 2017 is OK, 2015 after 2017 not.)
But consider installing a VM for the other version.
- Sure more initial farting around,
- but there will be no chance of inter-version "effects" and "fun."
- also snapshots, easy clean up and roll back.
- clones, (i.e. a pre-vs clone) - next time around skip the windows [and prefs] install work
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
I have had the two versions installed alongside one another for a couple of years now with no problems. Initially I used both extensively although now I'm using 2019 almost exclusively.
I installed 2017 first and I support the suggestion of others that it's best to do it in that order.
Be careful about making significant changes to a project/solution in 2019 if you want to open it subsequently in 2017, but normal code editing doesn't cause problems.
The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.
There are no problems having both versions side-by-side.
If you want to open a project/solution in a particular version, it may be better to open Visual Studio first, and then open the solution inside VS. Otherwise, it will probably use the last version installed.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
I'm retired now but when I was working, we had multiple VS20xx versions running on the same computer. Crucial to the process is not having any of the Visual Studio symbols pre-defined in your environment. Each version of the IDE should be activated from a DOS window/command line that is found in the menu tree for each compiler. Clever users (this would be you) can look at the contents of each menu item and cook up the same thing yourself and make them desktop shortcuts with your own local/personal modifications.
I haven't used VS2017 or VS2019 but I would assume that the same trick will still work.
P.S. Make absolutely sure that all remnants of any and all compilers do not exist in your environment before starting this. Type 'msdev' (or whatever it is now) at the command line and make sure it gives an error. Likewise, start from a menu item selection and verify that it gives an error.
No problems here, I have 2008, 2015, 2017 and 2019 all installed and they co-exists happily with each other on W10 X64.
One thing I will say though, since VS15 all installs have shiped with the "Visual Studio Version Detector", if you set up your file associations to load with that (Particularly your SLN files) then it will examine the SLN file (Or if it's a .cs file, will look in same folder for SLN/CSPROJ) and determine if possible which Visual Studio Version to open it with.
Failing that, I have icons on my desktop for all the versions, and I just drop the SLN from explorer onto the version I want to use when loading.
It's not as if my BMI is a problem: 24.5 is in the "Healthy Weight" area, though at the top end. But salads are as salads do - and worse I have to prepare them which means it's my fault if salad is boring.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!