Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix start menu folder clash of shortcut when both x86 and x64 are installed#5826

Merged
TravisEz13 merged 2 commits intoPowerShell:masterfrom
bergmeister:StartMenuFix_ArchitectureSpecific
Jan 11, 2018
Merged

Fix start menu folder clash of shortcut when both x86 and x64 are installed#5826
TravisEz13 merged 2 commits intoPowerShell:masterfrom
bergmeister:StartMenuFix_ArchitectureSpecific

Conversation

@bergmeister
Copy link
Contributor

@bergmeister bergmeister commented Jan 8, 2018

PR Summary

Fix clash of start menu shortcuts when x86 and x64 are both installed by appending " (x86)" for x86. This bug would affect 6.0.0. as well but is less severe. @SteveL-MSFT @TravisEz13

fixes #5825

Here is how it looks with the fix

image

PR Checklist

Note: Please mark anything not applicable to this PR NA.

…talled by appending " (x86)" for x86 to the .
<?define ProductSemanticVersionWithNameAndOptionalArchitecture = "$(var.ProductName)-$(env.ProductSemanticVersion)"?>
<?else?>
<?define UpgradeCode = "1d00683b-0f84-4db8-a64f-2f98ad42fe06" ?>
<?define ProductSemanticVersionWithNameAndOptionalArchitecture = "$(var.ProductName)-$(env.ProductSemanticVersion) ($(sys.BUILDARCH))"?>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason we are using a - and a _ in ProductVersionWithName?

If not, could we define ProductVersionWithName before this and use it instead of composing this from the components?

Copy link
Contributor Author

@bergmeister bergmeister Jan 8, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know. ProductVersionWithName was like that since 2016 if you do a blame on it. One would need to look at all usages and analyse them if one could change it. But to me it seems unrelated to the bug fix. But we can clean up the installer in a separate PR later?

@SteveL-MSFT SteveL-MSFT added this to the 6.1.0-MQ milestone Jan 8, 2018
@bergmeister
Copy link
Contributor Author

@SteveL-MSFT Do we need to document this minor issue for 6.0.0?

@bergmeister bergmeister changed the title Fix start menu folder clash of shortcut when both x86 and x64 are installed WIP (need to resolve merge conflict) Fix start menu folder clash of shortcut when both x86 and x64 are installed Jan 10, 2018
@SteveL-MSFT
Copy link
Member

cc @joeyaiello to determine if it's worth calling out for 6.0.0

Copy link
Member

@TravisEz13 TravisEz13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be reviewed again after merge conflict is resolved.

…o StartMenuFix_ArchitectureSpecific

Conflict resolution by taking both and made one small change: replaceed dash with space between product name and version in short cut name
# Conflicts:
#	assets/Product.wxs
@bergmeister bergmeister changed the title WIP (need to resolve merge conflict) Fix start menu folder clash of shortcut when both x86 and x64 are installed Fix start menu folder clash of shortcut when both x86 and x64 are installed Jan 11, 2018
@bergmeister
Copy link
Contributor Author

bergmeister commented Jan 11, 2018

Conflict resolution was trivial by taking the old and new change. But I made one small change: instead of the short cut saying PowerShell-6.x.y I replaced the dash with a space because PowerShell 6.x.y looks better to me.

@TravisEz13
Copy link
Member

@joeyaiello FYI

@TravisEz13 TravisEz13 merged commit bb09b88 into PowerShell:master Jan 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows installer: Start menu shortcuts are not architecture specific

3 participants