.NET February 2022 Update - .NET 6.0.2, .NET 5.0.14

[dcwhittaker]

Release Notes
6.0.2
5.0.14

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:

• dotnet/aspnetcore - for ASP.NET Core questions
• dotnet/efcore - for Entity Framework Core questions
• dotnet/sdk - for CLI tools and questions
• dotnet/runtime - for runtime, API, or installer issues and questions
• dotnet/winforms - for WinForms issues
• dotnet/wpf - for WPF issues
• nuget/home - for NuGet questions and issues

---

Status of availability of SDK on Microsoft's Linux feeds:

Distro	6.0.102	5.0.405	5.0.211
Ubuntu 18.04	✅	✅	✅
Ubuntu 20.04	✅	✅	✅
Ubuntu 21.04	✅	✅	✅
Centos 7	✅	✅	✅
Debian 9	✅	✅	✅
Debian 10	✅	✅	✅
Debian 11	✅	✅	✅
Fedora 33	✅	✅	✅
Fedora 34	✅	✅	✅
OpenSUSE 15	✅	✅	✅
Oracle	✅	✅	✅

Note: This list refers to the Microsoft-provisioned feeds (packages.microsoft.com) and does not in any way represent direct availability in distros (eg RHEL, Fedora).

Known Issues

If there are any more issues with this release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.

.NET 6.0.2

• There have been limited reports of a failure to install the update via Microsoft Update on Windows 11. The update fails with error code 0x80070643. A workaround is to install the package that is failing manually by downloading it from the .NET 6.0.102 x64 SDK download site, then scanning again.

• We are aware of an issue where some customers are unable to run Windows Forms apps built against 6.0.2. This appears a result of Windows Desktop servicing ref packs in 6.0.2. This was reported on 6.0.2 SDK update has broken WinForms apps winforms#6663 . A workaround is added to the Issue building with Windows Desktop 6.0.2 #7176

[dezsiszabi]

The same issue happens with this release when trying to update via Windows Update:

• Known Issue for the .NET 6.0.1 update: failure to install the .NET 6.0.1 update via Microsoft Update #7062
• .NET 6.0.1 / .NET 6.0.2 Windows Update fails with error 0x80070643  #7044

Manually downloading and installing works.

[suprak]

After updating to SDK 6.0.102 we are seeing that our WPF app references the following,

// PresentationCore, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (unresolved)
// PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (unresolved)
// System.Xaml, Version=6.0.2.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (unresolved)
// WindowsBase, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (unresolved)

However with SDK 6.0.101 (previous) our app referenced against,

// PresentationCore, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (unresolved)
// PresentationFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (unresolved)
// System.Xaml, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (unresolved)
// WindowsBase, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (unresolved)

Other common runtime references are not affected, just WPF related ones listed above (regardless of SDK version used to compile),

// System.Collections, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved)
// System.Collections.Specialized, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved)
// System.Configuration.ConfigurationManager, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (unresolved)
// System.Diagnostics.Process, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (unresolved)
...

Also in both cases the runtimeconfig.json looks like this,

{
  "runtimeOptions": {
    "tfm": "net6.0",
    "frameworks": [
      {
        "name": "Microsoft.NETCore.App",
        "version": "6.0.0"
      },
      {
        "name": "Microsoft.WindowsDesktop.App",
        "version": "6.0.0"
      }
    ],
    "configProperties": {
      "System.Reflection.Metadata.MetadataUpdater.IsSupported": false
    }
  }
}

This difference means that our app will not launch for folks that are still on the 6.0.1 runtime (they must update to 6.0.2 to resolve).

We see the following exception,

CoreCLR Version: 6.0.121.56705
.NET Version: 6.0.1
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Is this expected behavior?

[leecow]

@marcpopMSFT - any ideas on #7172 (comment)?

Update: Just found out this is a real issue. cc @RussKie as he's working on a WinForms fix now.

@suprak: A "workaround" is described at dotnet/winforms#6663 (comment) though it amounts to not running 6.0.2 for WinForms/WPF apps. The caveat is that this is a security release so if you're also affected by CVE-2022-21986, there is another consideration.

[rbhanda]

#7176 for Issue building with Windows Desktop 6.0.2 with added details for a workaround.

[twenzel]

6.0.2 breaks our web application build with error CS2015 'xy.png' is a binary file instead of a text file .
https://developercommunity.visualstudio.com/t/NET-SDK-60200-breaks-build-due-to-CS2/1667603?ref=native&refTime=1645007418972&refUserId=91f26041-a17a-4035-a156-3704387e57e3

[dhedey]

For the benefit of others searching here for a configuration error / breaking change new in dotnet 6.0.2, I've reported this issue: dotnet/runtime#61577 (comment)

Environment variable configuration set up with a prefix containing __ no longer matches to environment variables with that prefix. I've added a suggested workaround in the above linked comment.

The issue may surface as new/unexpected errors like Unhandled exception. System.ArgumentNullException: Value cannot be null. (Parameter 'connectionString') or other configuration-related exceptions.

[laxmanrapolu]

With 5.0.14 update our project ran into below error.
Cannot use file stream for [C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.14\Microsoft.NETCore.App.deps.json]: No such file or directory Error initializing the dependency resolver: A fatal error was encountered, missing dependencies manifest at: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\5.0.14\Microsoft.NETCore.App.deps.json

5.0.13 is working fine. We don't see deps.json file in 5.0.14 folder anymore.

[dcwhittaker]

Closed in favor of #7259