Release notes say that Dapper is compatible with .NET Standard 2.0. Why does it work with .Net Core 3.1? Since what release does it work?
OK - I understand. .Net Standard 2.0 asks for a minimum version (.Net core 2.0). 3.1 is therefore compatible.
Thanx DavidG!
Related
.NET 5.0 will replace .NET Core 3.x when it is released in November—and, thus, ASP.NET 5.0 will replace ASP.NET Core 3.x.
Edit: This question is based on a fundamentally incorrect assumption. While the next version of .NET Core will, in fact, be .NET 5.0, the next version of ASP.NET Core will be ASP.NET Core 5.0. See the answers from #Camilo-Terevinto and #omajid for details.
Despite this, as of Preview 8 (8.20414.8), packages, assemblies, and namespaces still contain AspNetCore in their names. For example, see the following NuGet packages:
Microsoft.AspNetCore.Http.Features
Microsoft.AspNetCore.Authorization
Microsoft.AspNetCore.DataProtection
Microsoft.AspNetCore.Razor.Language
If you go to the documentation for e.g. the Microsoft.AspNetCore.Http.Features namespace on learn.microsoft.com, however, you'll be redirected back to the ASP.NET Core 3.1 documentation with the warning:
The requested page is not available for ASP.NET Core 5.0 Preview. You have been redirected to the newest product version this page is available for.
Question: Do we have any evidence of what these packages, assemblies, and namespaces will be named in the .NET 5.0 release? Will they remain Microsoft.AspNetCore for backward compatibility, as the current namespaces suggest? Will they become Microsoft.AspNet for consistency with the product name, as the documentation suggests? Or does this remain TBD?
Background: Like other developers, I am working on the .NET 5.0 version of an open source library, and we aim to follow the same naming conventions as the underlying framework for the sake of familiarity, discovery, and consistency.
and, thus, ASP.NET 5.0 will replace ASP.NET Core 3.x.
That is not accurate, ASP.NET Core 5.0 will replace ASP.NET Core 3.x. The moniker that will change is .NET Core to .NET. Migration guide ASP.NET Core 3.x to ASP.NET Core 5.0.
Basically:
.NET Framework 4.8 -> .NET 5
.NET Core 3.1 -> .NET 5
ASP.NET Core 3.1 -> ASP.NET Core 5
thus, ASP.NET 5.0 will replace ASP.NET Core 3.x.
No, it won't. It's an unfortunate point of confusion, but it's not true.
Let me quote David Fowler, who is one of the ASP.NET Core architects:
There's no plan to change asp.net core to asp.net.
.NET Core becomes .NET 5, but ASP.NET Core stays as ASP.NET Core.
It seems that wexflow latest version v5.2.0 supports .net 4.6.1 and .net core 3.1
How to use wexflow with .net core 2.2?
Ref: https://wexflow.github.io/
I have an ASP NET MVC project with net471 target framework but I found nuget reference to Microsoft.AspNetCore.* or Microsoft.EntityFrameworkCore.*
It's correct? What problems can it entail?
It depends. First, I'm not sure if you're using terminology correct. Do you have an ASP.NET MVC 5 project or an ASP.NET Core project? If the former, then yes, it's very much incorrect. If the latter, then no it's fine, depending on the ASP.NET Core version.
.NET Framework 4.7.1 implements .NET Standard 2.0, which .NET Core 2.2 is also compatible with. Therefore, you can include ASP.NET Core 2.2 packages in a .NET Framework 4.7.1 project. Despite the name, an ASP.NET Core web app doesn't have to actually run on .NET Core. However, ASP.NET Core 3.0 or EF Core 3.0 would not work because those depend on .NET Standard 2.1, which no version of .NET Framework implements (and probably never will).
Googled a bit but couldn't find the .Net standard version for .Net core 2.2. Only version I got is,
Any hint please?
As you can see in the table you have uploaded, .NET Standard 2.0 is the latest available and it is fully supported by .NET Core v2.0. As you can see in this release doc. section, .NET Standard 2.1 will be supporting .NET Core 3.0 and also .NET Core 2.2. For the whole page check here.
In my opinion, you can go with .NET Standard 2.0 if you do not deal with extreme things (I mean recently added parts of .NET Core). This can yield some errors but still worth the try.
Is there a version of NPOI that works with ASP.NET Core 1.1 (not core 2.0). Every package is either for the Windows version or Core 2.0, which, in both cases, is not working with Core 1.1.
Thanks for helping
Likely not. The library is probably depending on .NET Standard 2.0 for .NET Core support. The earliest version of .NET Core to be cross-targetable is 2.0. For what it's worth, there's really zero reason to still be on .NET Core 1.1. It's not that big of a deal to upgrade, and honestly .NET Core 1.1 was not really viable for production use.