-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
.NET SDK (Microsoft.dotnet) installs wrong version #2105
Comments
Wasn't sure whether this was a CLI bug or a pkg bug. If needs to be moved to |
How does that jive w/ the actual binary being downloaded, though? (lowest arrow in screenshot) |
The binary name in this case is based on the "marketing version" or "display version" in Windows Apps & Features or Add/Remove Programs. The value highlighted in yellow is the registry entry made by that installer. There really isn't anything to force these values to conform with each other. When we built the "upgrade" behavior, we needed a consistent reliable mechanism for determining which version of a package was installed on the machine. The decision was made to do this based on the version reported from the registry. The current manifest schema 1.1 doesn't support the comparison outside of the "PackageVersion" attribute in the manifest, so we've been keeping that aligned so that the upgrade scenario isn't broken. In the next release we are aiming to be able to compare against the values in the manifest for "AppsAndFeatures" rather than the "PackageVersion". That would allow the package to be displayed as 6.0.202 in this case, and we would know based on the registry value and the "AppsAndFeatures" value in the manifest whether an upgrade should be performed or not. |
thanks for that explanation. Is this perhaps something I should file on the |
For now, I wouldn't worry about it. The .NET team is ramping up to start generating all their manifests, and the changes coming for "AppsAndFeatures" should alleviate most of the confusion. |
Since some releated issues were closed referencing this, I'm posting here. For some reason, my issues with the multiple attempted upgrades of the .NET 5 and 6 SDKs disappeared today. When I type Somehow (?!) today this has changed, and I have no idea what actually changed. None of the SDKs are showing up anymore. Just left with the rest of the apps that are already installed (false positives).
|
The .NET team has started publishing their manifests. We still have some work to do to improve the install/upgrade experience related to: There may also be some other improvements we can make here. |
Notice in this screenshot, winget reports it has found version 6.1.xxx on my machine and needs to install v6.2.xxx
However, when it pulls the pkg and begins downloading the installer, it installs 6.0.xxx instead
The text was updated successfully, but these errors were encountered: