f5fc0535ac
Fixes #8919 Preserve user shortcuts pinned to Taskbar during MSI upgrade by not removing shortcuts in this case (assuming the user has not changed the installation directory), see https://stackoverflow.com/a/33402698/1810304 This also requires the Guid to not always be re-generated, which PR #7701 originally added to ensure shortcuts get removed when RTM and preview are installed, the underlying problem was rather that RTM and preview shared the same GUIDs, therefore the GUIDs are hard-coded again but different for RTM and preview, therefore the shortcuts will still always get removed on uninstall. But this also means those GUIDs should change when the default installation directory changes, i.e. in PowerShell 7. Should we write the code to already take this into account that it does not get forgotten? Tested by first reproducing the issue by building installers locally (and bumping the patch version. Then the fix was applied to verify the solution, it. For this to take effect the version from which an MSI is being upgraded must have this fix already, i.e. if this fix got shipped in `6.2.1`, then on upgrading to it, the issue would still occur but when upgrading `6.2.1` to `6.2.2` the shortcut would start being preserved. I am wondering if we could maybe improve this to show effect earlier by trying to extract the used (auto-generated) GUIDs in the `6.2.0` and `6.2.0-rc` packages out and use them... Please not that we probably need to take this out for `7.0` because the base installation directory will change. This also assumes that the user has not specified a different installation directory on upgrade but this is a bit of an edge case where I think other things might break as well. |
||
|---|---|---|
| .. | ||
| additionalAttributions.txt | ||
| AppImageThirdPartyNotices.txt | ||
| av_colors_128.svg | ||
| Avatar.svg | ||
| avatar_128.svg | ||
| files.wxs | ||
| license.rtf | ||
| macDialog.png | ||
| patch-template.wxs | ||
| Powershell-preview.icns | ||
| Powershell.icns | ||
| Powershell_64.png | ||
| powershell_128.svg | ||
| Powershell_256.png | ||
| Powershell_av_colors.ico | ||
| Powershell_avatar.ico | ||
| Powershell_black.ico | ||
| Powershell_black_64.png | ||
| Product.wxs | ||
| ps_black_32x32.ico | ||
| ps_black_64.svg | ||
| ps_black_128.svg | ||
| pwsh.1.ronn | ||
| pwsh.manifest | ||
| README.md | ||
| WixUIBannerBmp.bmp | ||
| WixUIDialogBmp.bmp | ||
| WixUIInfoIco.bmp | ||
Use of Trademarked Logos
The assets in this folder are trademarked by Microsoft and don't fall under the same License as the source code.
Permitted Uses
Parties interested in using these logos can review the Use of Microsoft Copyrighted Material page. If the use falls into any of those categories, you can move forward with the use and will not need additional permission.
Third Party Permission Requests
If questions remain after reviewing the permitted uses page, please submit a request to Third Party Permissions. The people supporting this will direct the request depending upon the content.
If a request needs to be submitted to the Third Party Permissions, the request should include the following:
- A statement that the Use of Microsoft Copyrighted Material was reviewed and did not address the situation.
- A statement that Microsoft (and not a third party) is the owner of the logo at issue.
- Clear identification of the materials to be used (i.e., the picture of the book cover included by the author in the letter request should suffice).
- A description, including URLs of how they found or located the logo.
- A description of how the party intends to use or distribute the logo (i.e., that it is for the book cover of an instructional book on PowerShell).
- A description of how long the party needs to use the logo.