Update/Add .Net 7 SDK (Released today)

[ilya-scale]

Tool name

.Net SDK

Tool license

None

Add or update?

• [ ] Add
• [X] Update

Desired version

7

Approximate size

No response

Brief description of tool

.Net 7 SDK just came out and it would be nice to have it by default in the runner images and not to pull it

URL for tool's homepage

https://devblogs.microsoft.com/dotnet/announcing-dotnet-7/

Provide a basic test case to validate the tool's functionality.

No response

Platforms where you need the tool

• [ ] Azure DevOps
• [X] GitHub Actions

Runner images where you need the tool

• [ ] Ubuntu 18.04
• [ ] Ubuntu 20.04
• [X] Ubuntu 22.04
• [ ] macOS 10.15
• [ ] macOS 11
• [ ] macOS 12
• [ ] Windows Server 2019
• [ ] Windows Server 2022

Can this tool be installed during the build?

Yes

Tool installation time in runtime

No response

Are you willing to submit a PR?

No response

[mattjohnsonpint]

Per the Software and Image Support Policy:

Tool name	Installation strategy
.NET Core	2 latest LTS versions and 1 latest version. For each feature version only latest patch is installed

Presently, at least according to the image ReadMe files, we have:

Image	.NET SDK Versions Installed
ubuntu-22.04	6.0.402
ubuntu-20.04	3.1.120 3.1.202 3.1.302 3.1.424 5.0.104 5.0.214 5.0.303 5.0.408 6.0.402
macos-12	3.1.101 3.1.201 3.1.302 3.1.424 5.0.102 5.0.202 5.0.302 5.0.408 6.0.402
macos-11	3.1.101 3.1.201 3.1.302 3.1.424 5.0.102 5.0.202 5.0.302 5.0.408 6.0.402
windows-2022	3.1.120 3.1.202 3.1.302 3.1.424 5.0.104 5.0.214 5.0.303 5.0.408 6.0.402
windows-2019	3.1.120 3.1.202 3.1.302 3.1.424 5.0.104 5.0.214 5.0.303 5.0.408 5.0.413

Thus none of the images are following the stated policy.

What I would expect is that all non-deprecated images would have previously had exactly versions 3.1.424 6.0.402 and would be in process of updating to exactly versions 3.1.425 6.0.403 7.0.100. That's what the policy says anyway.

Or actually, if the intent is truly that every feature band is represented with its latest patch, then I would expect that the current versions would be exactly 3.1.120 3.1.202 3.1.302 3.1.424 6.0.110 6.0.203 6.0.305 6.0.402 and that we would be in process of getting exactly 3.1.120 3.1.202 3.1.302 3.1.425 6.0.111 6.0.203 6.0.306 6.0.403 7.0.100.

I would not expect to see .NET 5 at all, as it is not LTS and is not current.

This appears to be an ongoing problem. Can we please do something to resolve the underlying process?

Thanks.

[mikhailkoliada]

thanks, we will add 7 soon

[sommmen]

thanks, we will add 7 soon

Can you ballpark when this will happen? next week, next month?

[mikhailkoliada]

@sommmen next week

[mattjohnsonpint]

Just to mention for those that need .NET 7 and can't wait, you can still install it manually via:

- name: Install .NET 7 SDK
  uses: actions/setup-dotnet@v3
  with:
    dotnet-version: 7.x.x

Having it pre-installed is still important, as it speeds up build times and reduces network traffic.

[ghost]

I don't know what i'm doing wrong but it doesn't work for me.

And result

[mattjohnsonpint]

@msavara - Add spaces to indent dotnet-version

YAML is whitespace sensitive.

[MertUssakliMSFT]

Is .NET 7 still not included? https://github.com/actions/runner-images/blob/main/images/win/toolsets/toolset-2022.json

The Install .NET 7 SDK task works, but we now don't have the updated wasm-tools, which we have trouble installing as part of the pipeline.

[ShreyasJejurkar]

When this is going to happen!? Any ETA!?

[mikhailkoliada]

Deployed