Can Visual Studio Community 2015 be easily updated to Visual Studio Professional 2015
I have Visual Studio Community Edition 2015 installed on my drive D:.
I recently got a 1TB SSD for my C: drive and wanted to move VS to that drive. Long story shortened; it was a nightmare. Although I could uninstall VS, I could not get it to reinstall in any other location except for D:. After three days of trying, I gave up and reinstalled back to D:. I still could not get it to install correctly and some things are "damaged". Updates, etc. do not completely succeed because of the "damaged" module installation. I do not want to risk running the "Repair" option in the control panel again because that often makes it worse (damages more things); which leads to a several hour process of uninstalling & reinstalling. This question shows some of the installer/uninstaller problems: Installation errors in repair of Visual Studio 2015 Community Edition on Windows 10
I am now planning on reinstalling Windows 10 Pro in order to clean up this install.
I was planning on eventually getting Visual Studio Professional 2015.
Will I have similar problems upgrading from "Community Edition" to the "Professional" version?
I was hoping to open a dialog box, type in the license key and have the "Community Editon" become a "Professional" version. Is that possible or is a complete uninstall/reinstall how this upgrade would work?
Answer
(Disclaimer: I worked on Visual Studio 2015 including portions of the setup experience while at Microsoft)
It can, but it isn't as simple as entering an upgraded product key, you also need the media.
When you buy/license Visual Studio 2015 Professional or higher, you'll have access to the install media, usually an ISO file or vs_setup.exe web-downloader. Mount the ISO image and run Setup and you'll be prompted to upgrade (if I remember correctly). You cannot (to my knowledge) have a side-by-side install of Community and Professional Edition (unlike you can with the Express editions).
Personally I would just do a full uninstall of Community first, then a clean install of Professional - when I worked on the setup experience of VS2015 I logged a whole bunch of bugs that were experienced during in-version SKU upgrades (e.g. upgrading Community to Enterprise, then downgrading to Professional), such as project template item templates disappearing, etc. It wouldn't surprise me if these still caused issues - I don't think it's worth the risk.
Regarding Visual Studio 2017
Visual Studio 2017 now fully supports side-by-side installations of different SKUs (which is why the installation directory is %programfiles(x86)%\Microsoft Visual Studio 2017\Enterprise). So rather than doing an in-place upgrade from a lower SKU to a higher SKU, you install it as a separate install entirely. You'll need to manually move your settings and extensions over (or use the Microsoft Account-based settings synchronization feature).