I suggest you ...

Allow changing the nickname of the installation

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/351566/allow-changing-the-nickname-of-the-installation.html
You can set nicknames of installs in VS2017 but you cannot change those nicknames when modifying the installation features. This should be allowed.

121 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Edward Miller shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Eric Winn commented  ·   ·  Flag as inappropriate

        See manual solution at: https://developercommunity.visualstudio.com/solutions/384658/view.html

        Additionally, besides manually modifying the listed files you also have to rename various filenames and shortcuts scattered in several places on your system.

        I made the mistake of installing the Community Edition follwoed by the Professional Edition and failed to notice the "(2)" nickname appended to the Professional Edition.

        Also annoying is default file action, e.g. double clicking on a solution file will likely open the solution with whatever was installed first.

      • AF commented  ·   ·  Flag as inappropriate

        I'm only updating my VS2017 from 15.3 -> 15.7 -> 15.8. However, everything it is creating a new nickname (1, 2, 3) for the update. Why does it do that even it's not supposed to be different instances?

      Feedback and Knowledge Base