GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Enable MSI upgrades rather than side-by-side install by SteveL-MSFT · Pull Request #4259 · PowerShell/PowerShell

Conversation

@SteveL-MSFT

@SteveL-MSFT Steve Lee (SteveL-MSFT) commented Jul 14, 2017

Copy link
Copy Markdown
Member

MSI only works against A.B.C type version strings. So to enable beta.X to beta.X+1 upgrades, we have to use the AllowSameVersionUpgrades as they are all effectively 6.0.0 from MSI point of view.

Note that to get Wix toolset working on Win10, you may have to pass -sval to light.exe.

Fix #3946

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@SteveL-MSFT
Enable upgrades rather than side-by-side install
2c0b98a
@SteveL-MSFT Steve Lee (SteveL-MSFT) assigned Travis Plunk (TravisEz13) Jul 14, 2017
@SteveL-MSFT
Steve Lee (SteveL-MSFT) requested a review from Raghu Shantha (raghushantha) July 14, 2017 21:29
@msftclas Microsoft Contribution License Agreements (msftclas) added the cla-not-required label Jul 14, 2017
@SteveL-MSFT Steve Lee (SteveL-MSFT) changed the title Enable upgrades rather than side-by-side install Enable MSI upgrades rather than side-by-side install Jul 14, 2017
@raghushantha

Raghu Shantha (raghushantha) commented Jul 17, 2017

Copy link
Copy Markdown
Member

Steve Lee (@SteveL-MSFT) Changes look good. The only thing is to watch out for is that the 'ProductGuid' needs to be the same if you need upgrade to be supported.

For major version changes, ProductGuid can be changed
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
raghushantha
Raghu Shantha (raghushantha) approved these changes Jul 17, 2017
View reviewed changes
@SteveL-MSFT

Steve Lee (SteveL-MSFT) commented Jul 17, 2017

Copy link
Copy Markdown
Member Author

Raghu Shantha (@raghushantha) currently, Start-PSPackage has a default static ProductGuid so we should be good there.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@TravisEz13
Travis Plunk (TravisEz13) merged commit 0627409 into PowerShell:master Jul 17, 2017
@SteveL-MSFT
Steve Lee (SteveL-MSFT) deleted the msi-upgrade branch July 18, 2017 04:35
@ChristophB125

ChristophB125 commented Jul 18, 2017

Copy link
Copy Markdown

Steve Lee (@SteveL-MSFT) or Raghu Shantha (@raghushantha) It's great to have upgradability support but does this mean that we lose the ability of having multiple version installed side-by-side? We use older versions of PowerShell Core in our CI system (that is locked down and therefore not updated unless needed) and I always found it handy being able to repro on my local machine using the same version that is being used in CI in order to replicate the exact same behaviour.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@SteveL-MSFT

Steve Lee (SteveL-MSFT) commented Jul 18, 2017

Copy link
Copy Markdown
Member Author

ChristophB125 You can still have side-by-side by downloading the zip and extracting the contents in a secure location (this will always be supported).
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@ChristophB125

ChristophB125 commented Jul 20, 2017

Copy link
Copy Markdown

Thanks for the info. The self contained version in a zip file should be sufficient for our use case.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj-contribs/PowerShell that referenced this pull request Aug 6, 2026
@SteveL-MSFT @TravisEz13
Enable upgrades rather than side-by-side install (PowerShell#4259)
11ad688
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer
@raghushantha Raghu Shantha (raghushantha) raghushantha approved these changes
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

@TravisEz13 Travis Plunk (TravisEz13)

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

5 participants

@SteveL-MSFT @raghushantha @ChristophB125 @msftclas @TravisEz13
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.