-
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 February 2020 Update - 2.1.16, 3.0.3 and 3.1.2 #4280
Comments
Hi, we're having issues installing 2.1.16 on Ubuntu 16.04. Are the some dependency issues here?
|
Seeing the exact same situation on Ubuntu 19.10:
|
Hey folks, Keep an eye on the Linux repo checklist at the top of this issue. The upload service is really slow today and we're babysitting everything through. |
@TaraOverfield in repository dotnet/announcements (issue 151, February 2020 .NET Updates), the link to the Release Notes of .NET Core 3.1.2 doesn't work. It currently links to a file in tag 3.1.1, where it should be 3.1.2. The correct link is: https://github.com/dotnet/core/blob/master/release-notes/3.1/3.1.2/3.1.2.md |
@rbhanda needs to take a look |
Going from 3.1.1 to 3.1.2, our app failed to start:
Event log
|
Ok so I am running into this over five times a day, each time it seems to work if I try again in a few minutes. It's turning out to be a major productivity problem when we have multiple image builds per day on cluster - each one has to be manually checked and rerun when they fail. I am just wondering if the RPM repo will ever be reliable:
|
@yoshiya8 check out #4167 for general status on our effort to get the owners of the service to improve its reliability (and updates when we have them). That said... we haven't heard of flakiness the way you're experiencing it... the typical scenario is a period of downtime (up to 2 hours is "normal" for the RPM repos) but then back up for everyone. I've opened #4298 based on your comment to discuss more since it doesn't sound related to this release. |
When migrating from .NET Core 2.2 to 3.1, CORS does not appear to be working properly. I now receive an error saying
In the ConfigureServices method, I have:
In the Configure method, I have:
Note: The documentation on Microsoft's website is using outdated code, such as; UseMvc and IHostingEnvironment. https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1 |
hi, could you please provide upgrade steps from .net core 2.1 to 2.1.16 |
Experiencing the same issue |
Hello, |
How can install .NET 3.1.1 on ubuntu and not 3.1.2 ? Becasuse 3.1.2 has breaking changes |
@dicksonkimeu Based on a couple of Stack Exchange answers, you can do the following:
Replace Also, is the breaking change known? If not, have you reported it? |
I experience a very similar issue on Ubuntu 20.04. Does anyone know a fix for this?
|
@michalbilinski See #4360. Ubuntu 20.04 is currently not supported, packages for it should be available on 12 May. In the meantime, you can try the workarounds mentioned in that issue. |
You are right, thanks! |
3.1.2 Release Notes
3.1.2 Download
3.0.3 Release Notes
3.0.3 Download
2.1.16 Release Notes
2.1.16 Download
Blog posts
.NET Core
Please report any issues you find with 2.1.16, 3.0.3 or 3.1.2, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:
We are experiencing delays in pushing Linux feeds. Here is the list of repositories we are trying to push and as the release is progressing, we will tick them off as each is resolved.
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: