Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improper versions being reported by "upgrade" - Sql Server Management Studio #828

Closed
eidylon opened this issue Mar 29, 2021 · 3 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Milestone

Comments

@eidylon
Copy link

eidylon commented Mar 29, 2021

Brief description of your issue

When running winget upgrade, it is showing me the wrong versions for SSMS, and showing an upgrade when there isn't.

Steps to reproduce

I have SSMS latest version installed
I run winget upgrade to list available upgrades

Expected behavior

Would show updates available to apps I have that are not the latest version. Needs to compare the same version numbers (the same "source") for installed vs. available.

Actual behavior

C:\>winget upgrade
Name                         Id                                  Version      Available Source
-----------------------------------------------------------------------------------------------
Arduino IDE                  ArduinoLLC.ArduinoIDE               1.8.42.0     Latest    msstore
SQL Server Management Studio Microsoft.SQLServerManagementStudio 15.0.18369.0 18.8      winget

C:\>

You can see that it shows the installed version as 15.0.18369.0, and shows the latest version as 18.8.

However, looking at the About screen in SSMS, you can see these actually are the same verion.
image

So it seems that for the current "Version" it is showing the build version, whereas for the latest "Available", it is showing the "friendly" version. As a result, it thinks there is an update when there isn't, because it is comparing limes to bananas.

Because of this, if I try to run the upgrade, it fails like so...

C:\>winget upgrade Microsoft.SQLServerManagementStudio
Found SQL Server Management Studio [Microsoft.SQLServerManagementStudio]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://go.microsoft.com/fwlink/?LinkID=840946
  ██████████████████████████████   898 MB /  898 MB
Successfully verified installer hash
Starting package install...
Installer failed with exit code: 3221225477

C:\>

Environment

[winget --info]
Windows Package Manager version: v0.2.10191 Preview
Windows: Windows.Desktop version: v10.0.19042.870
Package: Microsoft.DesktopAppInstaller version: v1.11.10191.0

Any other software?
@ghost ghost added the Needs-Triage Issue need to be triaged label Mar 29, 2021
@jedieaston
Copy link
Contributor

This can be fixed by putting the proper build number in the manifest as opposed to the "marketing" version number, which is how we've been doing it for Visual Studio.

@jedieaston
Copy link
Contributor

Looks to be resolved now that all of the PRs have cleared. Is it behaving correctly on your end now too?

PS C:\Windows\system32> winget list --id Microsoft.SQLServerManagementStudio
Name                         Id                                  Version
-----------------------------------------------------------------------------
SQL Server Management Studio Microsoft.SQLServerManagementStudio 15.0.18369.0
PS C:\Windows\system32> winget upgrade --all
No applicable update found.
PS C:\Windows\system32>

@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels Mar 30, 2021
@eidylon
Copy link
Author

eidylon commented Mar 30, 2021

Yup, just checked, and it is now no longer erroneously listing SSMS as an available upgrade. 👍🏼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

3 participants