-
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 Core March 2020 Updates – 2.1.17 and 3.1.3 #4453
Comments
This included? |
dotnet/efcore#20279 was submitted recently. This did not make it to the current release. |
Chocolatey fails for 3.1.3, need to worry or not? You have dotnetcore v3.1.2 installed. Version 3.1.3 is available based on your source(s).
dotnetcore not upgraded. An error occurred during installation:
The remote server returned an error: (403) Forbidden. Forbidden
dotnetcore package files upgrade completed. Performing other installation steps.
The upgrade of dotnetcore was NOT successful.
dotnetcore not upgraded. An error occurred during installation:
The remote server returned an error: (403) Forbidden. Forbidden Regards. |
The 3.1.3 Release Notes links to an internal page for macOS Notarization Issues instead of https://docs.microsoft.com/en-us/dotnet/core/install/macos-notarization-issues |
Thanks @mletterle - link fixed. |
@fwd079 - the Chocolatey packages are community maintained and not "official". We'll check a few things on this side to make sure nothing is obviously out of sorts. After that, it will be up to the maintainers. Update: If I run @riezebosch - any thoughts? |
something went wrong on publishing the package, it seems available but you cannot download it: https://packages.chocolatey.org/dotnetcore-runtime.install.3.1.3.nupkg Pushed an update |
Just successfully installed 3.1.3 and SDK 3.1.201 via Chocolatey. Looks like that did it. Thanks @riezebosch! /cc @rbhanda |
So it was on this side, well I am glad then, since that made sorting out a swift thing, checked this morning and working as expected and installed. Thanks @riezebosch for looking into it. Regards. |
The following relates to 3.1.3. When restoring an fsproj project with SDK version 3.1.201, I am seeing this:
If I use 3.1.103, it works fine. Only 3.1.201 has the problem. I see the same pattern with release 3.1.2. Problem exists in 3.1.200 but it works in 3.1.102. I have tried both in Docker to isolate any VS-related issues. I wonder if the problem has to do with the version of MSBuild tools/dependencies in .201 and .200 being outdated? But they're good enough for .103 and .102, which I note targets a slightly older Visual Studio. Command used was I get the same problem running under a Docker build with image Is there any more information I can provide? Should I file an issue on this somewhere?
|
[Memory Leak] ex: public static List RunTaskAndReturnStdout(string fileName, string arguments, string workingDirectory = "") |
Closed in favor of #4675 |
3.1.3 Release Notes
3.1.3 Download
2.1.17 Release Notes
2.1.17 Download
Blog posts
.NET Core
Please report any issues you find with 2.1.17 or 3.1.3, 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 Linux feeds:
Here is a list of issues that we are tracking and working to resolve with the Feb 2020 release. We'll tick them off as each is resolved. See any linked issue for progress or resolution details.
The text was updated successfully, but these errors were encountered: