.NET August 2024 Update - .NET 8.0.8, .NET 6.0.33

[rbhanda]

.NET August 2024 Update

Release Notes

• 8.0.8
• 6.0.33

Status

Asset Type	8.0.8	6.0.33	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
Fedora 40
OpenSUSE 15
Ubuntu 20.04
Ubuntu 22.04
Ubuntu 23.04
Ubuntu 24.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

[T3rminat0r]

Just as general Feedback... the list of "Changes" for both releases is ... basically non-existant, apart from listing the two CVEs for the 8.0.8 release, the "release-notes" are a list of where/how to obtain the most recent release, rather than actual release notes, telling us what changed compared to the last version!? ... might just be me wondering, tho ...

[libreo-abrettschneider]

And AGAIN our build pipeline breaks cause of analyzer changes similar to https://github.com/dotnet/core/issues/9309#issuecomment-2112177085 "error IDE0073: A source file contains a header that does not match the required text"

Yes it is an error that we need to fix, but a patch release should not break things that worked before. Is there any way to "fix" the analyzers to a specific version?

Also it breaks docker image builds for us: https://github.com/dotnet/msbuild/issues/10518

[lischetzke]

Question regarding the new versions for Windows. We're running Server 2019 and noticed that the old .NET Hosting Bundles (6.0.32 and 8.0.7) install multiple packages (Windows Server Hosting, .NET Runtime, ASP.NET Core). Typically the installer will remove the old versions and install the new versions.

This time the Hosting Bundle installer installed the new version successfully, but did not remove the old versions. Add/Remove programs and dotnet --info are still showing the old versions for .NET Runtime and ASP.NET Core. dotnet --info shows the newly installed versions too. The Add/Remove Programs shows Windows Server Hosting in the correct version (6.0.33 and 8.0.8) and only that version, as expected.

A clean install of the Hosting Bundle only shows Windows Server Hosting in Add/Remove Programs. Checking the reg keys it seems that the old versions added multiple keys in HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall with Bundle* values. The new one only creates this key for Windows Server Hosting. .NET Runtime and ASP.NET Core do not get keys with Bundle* values like the previous versions.

Is it expected, that .NET Runtime and ASP.NET Core are not listed/updated in Add/Remove Programs anymore? Shouldn't the installer update/uninstall older versions like before?

---

Before update:

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

After update:

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.33 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.33 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

[Rockvolleyball]

Having the same issues over here as @lischetzke describes. Installation is not going as expected, ending up in mixed versions.

[SergBarkovskii]

Hey there @rbhanda Any expectations when 8.08 will be available via Linux Packages (Microsoft distribution) on Debian, Fedora and so on? Thank you

[renevanderheijden]

I know Debian 9 (armhf) is not supported anymore, but since version 6.0.33 starting an application results in a segmentation fault.

Failed to load /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.33/libcoreclr.so, error: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.27' not found (required by /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.33/libcoreclr.so)
Segmentation fault

I didn't expect breaking changes like these in LTS versions, even if the OS is not supported anymore.

[nbren007]

I know Debian 9 (armhf) is not supported anymore, but since version 6.0.33 starting an application results in a segmentation fault.

Failed to load /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.33/libcoreclr.so, error: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.27' not found (required by /usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.33/libcoreclr.so)
Segmentation fault

I didn't expect breaking changes like these in LTS versions, even if the OS is not supported anymore.

I have this issue. Have you found any resolution?

[renevanderheijden]

@nbren007 Unfortunately not... We just keep on using version .31, until we migrate our application to a newer .NET version.

[rbhanda]

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

[deepu9890]

.NET 8.0.8 and .NET SDK 8.0.400 after patch update the application failing with exception could not load file or assembly Microsoft.AspNetCore.SignalR.Client.Core etc.. We load all dlls from installation location and with the new patch update causing issues on client machines and forcibly asking for upgrade. Can anyone suggest or help us.

Microsoft.AspNetCore.SignalR.Client.Core should be update to version 8.08,

see exception msg: "Could not load file or assembly 'Microsoft.AspNetCore.SignalR.Client.Core, Version=8.0.8.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'

[lischetzke]

Is it expected, that .NET Runtime and ASP.NET Core are not listed/updated in Add/Remove Programs anymore? Shouldn't the installer update/uninstall older versions like before?

Update on that issue from my side. Updating .NET using WSUS/Windows Update did the trick and ASP.NET as well as .NET Runtime are again showing up in Add/Remove Programs in the correct version. The previous versions were removed cleanly in the programs list and using dotnet --info.

ooking at the update in the Microsoft Update Catalog it seems to me like Windows Update is installing every component separately. This might be something to consider if someone previously installed/updated .NET using the Hosting Bundle and now experiences this issue. Windows Update will not install the components again, if the latest Hosting Bundle was applied, but ASP.NET or .NET Runtime is not shown in the programs list. Instead it will "correct" the issue when installing an update.

Windows Update will show an available update if older .NET versions were found, i.e. because of this issue, and the update can be reapplied by an update. This could be validated with a system that had this issue where the newest Hosting Bundle was installed but an older version of .NET Runtime was still installed on the system.

This seems to be the case even for the 2024-10 .NET Hosting Bundle which in my opinion is still an issue.

@Rockvolleyball maybe this is useful information or a possible solution for you.

[Rockvolleyball]

Thanks for the update @lischetzke

For me Windows Update is no option.

Think I found out what is happening, see this post: https://github.com/dotnet/core/issues/9555