winget install -e --install Microsoft.dotnet -v 5.0.303 - No version found matching: 5.0.303

[vatsan-madhavan]

trafficstars

> winget install -e --id Microsoft.dotnet -v 5.0.303  arm64 ↑1  ~1 
No version found matching: 5.0.303

Looks like the latest that winget installs is 5.0.301:

> winget install -e --id Microsoft.dotnet
Found Microsoft .NET SDK [Microsoft.dotnet]
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://download.visualstudio.microsoft.com/download/pr/ced7fd9b-73b9-4756-b9a4-e887281b8c82/7ab0a8e6e8257f1322c6b63a5e01fcb9/dotnet-sdk-5.0.301-win-x64.exe
  ██████████████████████████████   145 MB /  145 MB
Successfully verified installer hash
Starting package install...
Successfully installed

[vatsan-madhavan]

Is there a process yet to automatically update winget manifests at https://github.com/microsoft/winget-pkgs/commits/master/manifests/m/Microsoft/dotnet when new SDK's are released? If not (yet), then something to consider. Given winget is now integrated into Windows, my 2c is that we should strive to make acquiring .NET SDK's using winget somewhat consistent.

[marcpopMSFT]

@rbhanda @leecow any suggestions here as part of the release tooling?

[leecow]

Not on our radar to consider at the moment but certainly something to think about how it might be improved.

[yooakim]

It would be soo nice if one could use winget to install all versions of the .NET SDKs. At the moment that is only possible for .NET 6. SDK

I'm supporting many developers and if one could install the proper SDKs via winget it would make life easier :-)

When moving from one machine to another if is very convenient to do a winget export installed.json and then winget import installed.json on a new machine. At the moment this does not work for .NET SDKs.

[marcpopMSFT]

Old issue triage: we now publish official packages so this should be resolved.