.NET February 2024 Update - .NET 8.0.2, NET 7.0.16, .NET 6.0.27

[rbhanda]

.NET February 2024 Update

Release Notes

• 8.0.2
• 7.0.16
• 6.0.27

Status

Asset Type	8.0.2	7.0.16	6.0.27	Notes
Installers/Binaries	✅	✅	✅
Snaps	✅	✅	✅
Linux Packages (Microsoft distribution)			The list below refers to the Microsoft-provisioned feeds (packages.microsoft.com) and does not in any way represent direct availability in distros (eg RHEL, Fedora).
Centos 7	NA	✅	✅
Centos 8	✅	✅	✅
Debian 10	✅	✅	✅
Debian 11	✅	✅	✅
Debian 12	✅	✅	✅
Fedora 37	✅	✅	✅
Fedora 38	✅	✅	✅
Fedora 39	✅	✅	✅
OpenSUSE 15	✅	✅	✅
Ubuntu 20.04	✅	✅	✅
Ubuntu 22.04	✅	✅	✅
Ubuntu 23.04	✅	✅	✅

Issues

Please report any issues you find either by responding to this issue, creating a new issue or creating a new issue in one of the following repos:

• ASP.NET Core: dotnet/aspnetcore
• Entity Framework Core: dotnet/efcore
• .NET CLI/SDK dotnet/sdk
• .NET runtime dotnet/runtime
• Winforms: dotnet/winforms
• WPF: dotnet/wpf
• NuGet: nuget/home
• Containers: dotnet/dotnet-docker
• Winget: microsoft/winget-pkgs

Known Issues

[wasabii]

https://github.com/dotnet/razor/issues/9935

[Hrxn]

[version confusion cleared up, thanks to @vernou]

[evgenyvalavin]

https://github.com/dotnet/sdk/issues/38769

[darthkurak]

Does the SDK 8.0.2 bump somehow use a version of MSBuild.StructuredLogger ? I have FAKE scripts that started to fail after upgrading to the 8.0.2 SDK

Unsupported log file format. Latest supported version is 16, the log file has version 17.

(I have MSBuild.StructuredLogger (2.1.815))

And the same script is working on 8.0.1

[Hrxn]

[ removed broken image]

Yet, I get this here

C:\>dotnet --version
8.0.102

C:\>

What's that supposed to mean?

Okay, just for kicks and giggles, I downloaded and ran the SDK x64 Installer package, you know, the thing, the one behind the big, fat purple download button on https://dotnet.microsoft.com/en-us/download.

And, lo and behold:

PS C:\> dotnet --version
8.0.200
PS C:\>

I assume this is intentional, but I'm not sure, maybe this should be mentioned somewhere, just to prevent confusion in the first place 🤪 PS. Don't remember this being the case with .NET 8.0.1, though.

[vernou]

@Hrxn A .NET Runtime version can have multiple SDK version. See How .NET is versioned for more information.

It's the case with .NET 8.0.2 that has the two SDK versions 8.0.200 and 8.0.102 (see .NET 8 download page).

---

Windows Update update the runtime, but not the SDK. I think it's a VS update (can be managed by Windows Update) that updated your SDK.

[Hrxn]

Thank you @vernou , that was exactly what I was looking for. .NET documentation article explaining the versioning. Appreciate it.

[jattinc]

Github actions failing because 8.0.201 not available to download.

https://dotnetcli.azureedge.net/dotnet/Sdk/8.0.201/dotnet-sdk-8.0.201-win-x64.zip.

[AlexeyRaga]

Same for Linux, lots of CI is broken because 8.0.201 is not available to download.

https://dotnetcli.azureedge.net/dotnet/Sdk/8.0.201/dotnet-sdk-8.0.201-linux-x64.tar.gz

[baronfel]

Does the SDK 8.0.2 bump somehow use a version of MSBuild.StructuredLogger ? I have FAKE scripts that started to fail after upgrading to the 8.0.2 SDK

Unsupported log file format. Latest supported version is 16, the log file has version 17.

(I have MSBuild.StructuredLogger (2.1.815))

And the same script is working on 8.0.1

Yes, most quarterly SDK releases will bump the format as we add new events. However, the next quarter's release (May) should be the first one where the format supports forward compatibility, so this blocking error should go away once you update to that series of MSBuild Structured Logger packages.

[mairaw]

Same for Linux, lots of CI is broken because 8.0.201 is not available to download.

https://dotnetcli.azureedge.net/dotnet/Sdk/8.0.201/dotnet-sdk-8.0.201-linux-x64.tar.gz

@AlexeyRaga @jattinc the team is aware of the issue and is looking into it. The workaround would be to not use 8.0.x and specify a specific version other than 201. We'll let you know when things are back to normal.

[rbhanda]

Same for Linux, lots of CI is broken because 8.0.201 is not available to download. https://dotnetcli.azureedge.net/dotnet/Sdk/8.0.201/dotnet-sdk-8.0.201-linux-x64.tar.gz

@AlexeyRaga @jattinc the team is aware of the issue and is looking into it. The workaround would be to not use 8.0.x and specify a specific version other than 201. We'll let you know when things are back to normal.

Hi @AlexeyRaga @jattinc , apologies for the delay in fixing this issue. https://dotnetcli.azureedge.net/dotnet/Sdk/8.0.201/dotnet-sdk-8.0.201-linux-x64.tar.gz should be working and available now.

[csehammad]

Encountered a breaking change in #aspnet core MVC after updating to .NET 8.0.2 - "Index view not found" error. Resolved by rolling back the update. Details & discussion here: https://techcommunity.microsoft.com/t5/net-runtime/net-8-0-2-update-causes-asp-net-core-mvc-index-view-not-found/m-p/4058976#M382

[meenzen]

There does not appear to be an oci-image mcr.microsoft.com/dotnet/sdk:8.0.201 for the latest sdk update. Will this be published soon?

[axylophon]

Does anybody else also has problems with dotnet format?

We use a Blazor WASM application and use dotnet format --verify-no-changes in our CI Pipeline. We also have an .editorconfig file in place.

Since 8.0.201 we get lots of false positives that Methods/Properties in razor.cs code behind files are not used. But they are all used in the .razor file.

If we revert to 8.0.101 the issue is gone.

[joncham]

I am seeing csc hang/delay for 20s when run with the /shared argument. I assume it's trying to launch the server process and failing or failing to connect.

https://github.com/dotnet/roslyn/issues/72180

[Devqon]

Encountered a breaking change in #aspnet core MVC after updating to .NET 8.0.2 - "Index view not found" error. Resolved by rolling back the update. Details & discussion here: https://techcommunity.microsoft.com/t5/net-runtime/net-8-0-2-update-causes-asp-net-core-mvc-index-view-not-found/m-p/4058976#M382

We have also experienced this issue, even creating a completely clean/new web project fails with this error. Downgrading to 8.0.102 works. I see there is a patch released (201) but it does not mention this bug

[cmenzi]

The package is still not available here:

• https://packages.microsoft.com/ubuntu/22.04/prod/pool/main/d/dotnet-sdk-8.0/
• https://packages.microsoft.com/ubuntu/22.04/prod/dists/jammy/main/binary-amd64/Packages

apt-get install -yq dotnet-sdk-8.0=8.0.201-1 fails

[rbhanda]

closing in favor of https://github.com/dotnet/core/issues/9214