Skip to content

start menu folder includes version number #5884

Description

I installed the 6.0 release and the start menu folder that is created is called PowerShell-6.0.0 will the folder name change with future versions? Is this because side-by-side installs are possible? Wouldn't it be better to just have it called PowerShell 6? The dash makes it look a bit weird as well.

Activity

  1. added
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    on Jan 12, 2018
  2. iSazonov commented on Jan 12, 2018

    @iSazonov
    Collaborator

    Yes, it is for side-by-side installs - you can easily install preview versions side-by-side with the release version.
    I believe the start menu folder and directory names is good until anybody discover a broken scenario.

  3. Stanzilla commented on Jan 12, 2018

    @Stanzilla
    ContributorAuthor

    Well, may I suggest just removing the hyphen then? Probably looks better :)

  4. bergmeister commented on Jan 12, 2018

    @bergmeister
    Contributor

    The reason why there is a folder is not only side by side but also that the folder can contain e.g. an x64 and x86 version. For 6.0 it is a known issue that the start menu will contain only either x64 or x86 but this has already been fixed for the upcoming version. But I think we can consider replacing the dash with a space (I removed the dash already from the short cut name itself already). It is good to include the full version because it makes it easy for non-technical people to figure out their exact version should a patch be required at some point (e.g. due to new security vulnerabilities in .Net Core).

  5. bergmeister commented on Jan 12, 2018

    @bergmeister
    Contributor

    Benjamin Staneck (@Stanzilla) The fix with the hyphen would be very easy. Do you want to do it yourself? The fix would be on this line to replace the ProductSemanticVersionWithName variable with ProductSemanticVersionWithNameAndOptionalArchitecture
    You can simply push that fix to your branch and on the AppVeyor build you can download the artifacts to test your fix before submitting the PR.

  6. Stanzilla commented on Jan 12, 2018

    @Stanzilla
    ContributorAuthor

    Christoph Bergmeister (@bergmeister) Here, right?

    <Product Id="$(var.ProductGuid)" Name="$(var.ProductSemanticVersionWithName)-$(sys.BUILDARCH)" Language="1033" Version="$(var.ProductVersion)" Manufacturer="Microsoft Corporation" UpgradeCode="$(var.UpgradeCode)">

  7. bergmeister commented on Jan 12, 2018

    @bergmeister
    Contributor

    No, line 178 as per the link in my comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-FixedThe issue is fixed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions