Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upSpecify verb for context menu to avoid overriding the default verb #7932
Conversation
This comment has been minimized.
This comment has been minimized.
|
If we update current "broken" installation with the new installer what will happen to the old "open" key? I'd expect that we remove it. |
iSazonov
requested review from
TravisEz13 and
SteveL-MSFT
Oct 3, 2018
iSazonov
assigned
TravisEz13
Oct 3, 2018
This comment has been minimized.
This comment has been minimized.
|
During an upgrade, old components get removed, therefore the old registry keys 'should' get removed. |
This comment has been minimized.
This comment has been minimized.
|
@bergmeister the change looks fine, but will wait for your testing results |
This comment has been minimized.
This comment has been minimized.
|
@SteveL-MSFT @iSazonov Import-Module .\build.psm1; Start-PSBuild -Clean -CrossGen -PSModuleRestore -Runtime win7-x64 -Configuration Release; Import-Module .\tools\packaging
Start-PSPackage -Type msi -WindowsRuntime 'win7-x64' -SkipReleaseChecks -Version 6.1.0 # from master
Start-PSPackage -Type msi -WindowsRuntime 'win7-x64' -SkipReleaseChecks -Version 6.1.1 # from PR branch
Start-PSPackage -Type msi -WindowsRuntime 'win7-x64' -SkipReleaseChecks -Version 6.2.0 # from PR branch |
bergmeister commentedOct 3, 2018
•
edited
PR Summary
Fix is to specify the verb (pwsh) for the context menu, otherwise there can be special cases (see issues) where it overrides the default verb, see comment here for details. Thanks to @GeeLaw for the helpful comments.
I will manually check in the next days that the installer will remove the old
openentries during upgrade.PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests