Skip to content
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 December 2020 Update - 5.0.1 #5719

Closed
rbhanda opened this issue Dec 8, 2020 · 17 comments
Closed

.NET Core December 2020 Update - 5.0.1 #5719

rbhanda opened this issue Dec 8, 2020 · 17 comments

Comments

@rbhanda
Copy link
Contributor

rbhanda commented Dec 8, 2020

Release Notes

Please report any issues you find with .NET 5.0.1, 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:

Distro 5.0.1
Ubuntu 16.04
Ubuntu 18.04
Ubuntu 20.04
Ubuntu 20.10
Centos 7
Debian 9
Debian 10
Fedora 32
Fedora 33
OpenSUSE 15
SLES 12
SLES15

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 the December 2020 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.

@adamralph

This comment has been minimized.

@adamralph

This comment has been minimized.

@rbhanda rbhanda pinned this issue Dec 8, 2020
@rbhanda rbhanda mentioned this issue Dec 8, 2020
3 tasks
@RheaAyase
Copy link
Member

RheaAyase commented Dec 8, 2020

Yey, we've got checkboxes on distributions that don't even have 5.0.0 yet (again) :D
(Please differentiate between proper support, and binary release only.)


For example this

Status of availability of SDK on Linux feeds:

...could become

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

@rbhanda
Copy link
Contributor Author

rbhanda commented Dec 8, 2020

Hi @RheaAyase The checkboxes have a note added
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).

I have also updated the description for the list as you suggested.

@maliming
Copy link

maliming commented Dec 9, 2020

hi @rbhanda

I set the version of the Microsoft package globally in the Directory.Build.props file, but I found that not all packages have released version 5.0.1.

https://www.nuget.org/packages/Microsoft.Extensions.Logging/
https://www.nuget.org/packages/Microsoft.Extensions.Localization/

All ms packages in 3.x have the same version. Has this rule changed in the 5.x version?

Thanks.

@rbhanda
Copy link
Contributor Author

rbhanda commented Dec 9, 2020

hi @maliming these packages were not updated with 5.0.1 Release. You can find a list of all updated nuget packages on 5.0.1 release notes

@martin-honnen
Copy link

The early announcements for .NET 5 features (in https://devblogs.microsoft.com/dotnet/introducing-net-5/) included a feature "Java interoperability will be available on all platforms.", this doesn't seem to have made it in any way into .NET 5. Are there any plans to have it in .NET 6? For the .NET framework and Mono IKVM provided that Java interoperability.

@FIrgolitsch
Copy link

FIrgolitsch commented Dec 10, 2020

Is there any timeline for a CentOS 8 release?

@RheaAyase
Copy link
Member

@FIrgolitsch As a low priority bugfix 5.0.1 will be released with the January update, since it wasn't possible to build it from source until a few days ago, so there is a bit of catchup to do between 5.0.0 (released two days ago) and 5.0.1

@omajid
Copy link
Member

omajid commented Dec 10, 2020

Is there any timeline for a CentOS 8 release?

Builds were already done: https://koji.mbox.centos.org/koji/packageinfo?packageID=3232. Not sure when they go live.

Edit: i read the question wrong. Sorry.

@RheaAyase
Copy link
Member

You can follow RHEL/Fedora details in this tracking ticket: #5596

@phillip-haydon
Copy link

Microsoft.AspNetCore.Authorization 5.0.1 is broken,

Just including this in a project with no authorization causes it to fail on startup due to missing configuration.

@ferraridavide
Copy link

Can't seem to be able to create ADO.NET Entity Data Model, is it not supported?

Step to recreate: Create C# Console Application with .NET 5.0 -> Add New Item -> Data -> ADO.NET Entity Data Model -> Error: "The project's target framework does not contain Entity Framework runtime assemblies."
image

@BhanuNexus
Copy link

Hi Team,

Previously, example with .NET Core 3.1 with every release all packages were updated like 3.1.1, 3.1.2 etc.,
We were including version like <AspNetVerion>3.1.10</AspNetVersion> in Directory.Build.props and use it every where.
We used to update it in one place and all packages were updated to the latest.

OrchidCore does something similar.

With .NET 5, is this changed? I see that only few packages were updated.

@shanekunz
Copy link

shanekunz commented Dec 22, 2020

I would create an Azure support ticket for this, but it costs $30 for a support membership. .NET 5 (Early Access) web app Azure deployments via git are now failing. I was able to deploy .NET 5 web apps before this release. Here's some relevant logs, I can send the full logs to anyone interested, I'm not sure why it's referencing the previous SDK/runtime release in this message, but I don't hardcode the patch number anywhere in my project:

remote: D:\Program Files (x86)\dotnet\sdk\5.0.100\Sdks\Microsoft.NET.Sdk.Razor\extensions\mvc-3-0\Microsoft.AspNetCore.Mvc.Razor.Extensions.dll
remote:
remote: ...............
remote: It was not possible to find any compatible framework version
remote: The framework 'Microsoft.NETCore.App', version '5.0.0' was not found.

@kaylumah
Copy link

@BhanuKorthiwada my team does something similar which makes it very easy to manage the dependencies. Having said that most of my projects arre still on netcoreapp3.1 since that is the latest lts version at the moment.
I came looking because for a POC I did not bother specifying target framework for it. I found that not all Microsoft.Extensions.FileProviders were updated, is there a reason for this change?

@rbhanda rbhanda unpinned this issue Jan 12, 2021
@rbhanda
Copy link
Contributor Author

rbhanda commented Jan 12, 2021

Closing in favor of #5838

@rbhanda rbhanda closed this as completed Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests