-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET April 2021 Update - .NET 5.0.5, .NET Core 3.1.14 and .NET Core 2.1.27 #6129
Comments
Can't get ".NET Desktop Runtime 5.0.5" by windows update and My Visual Studio 16.9 still install ".NET SDK 5.0.201" |
I am getting below unit test execution error both in Visual Studio IDE 2019 (16.9.3) and command line through vstest.console.exe (16.9.1). This happens even after installing the latest .NET 5.0.5 (5.0.202 SDK). Any idea? I even tried to debug into the Newtonsoft 13.0.1 but only to find the constructor just quits and throws the exception. The module runs fine during runtime. The failing unit test project is using the following:
It is testing components/apps that are .NET Core 2.1 targeting .NET FW 4.6.2. Below is the stack trace from the unit test command line execution Error Message: |
Version 3.1.14 is missing in the release json: https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/3.1/releases.json . |
Hello @XieJJ99 releases.json is updated for 3.1 |
dotnet-runtime-2.1 on Ubuntu 18.04 installs 2.1.26 instead of 2.1.27: dotnet/runtime#52331 |
closing in favor of #6247 |
Release Notes
5.0.5
3.1.14
2.1.27
Please report any issues you find with .NET 5.0.5 either responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Status of availability of SDK on Microsoft's Linux feeds:
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 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.
The text was updated successfully, but these errors were encountered: