As all know, we can use LimitedConcurrencyLevelTaskScheduler at .net Framework 4.x.
Official LimitedConcurrencyLevelTaskScheduler.cs
It is an implementation for .net core?
Related
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!
Does anyone know about a decompiler tool for .net core which is written in .net core?
All the tools I found are written in .net framework.
My application is written in .net core and I prefer not to require my users to install also .net framework.
Thanks
.NET Reflector
supports C#7, .NET 4.7.2, and .NET Core and Standard.
here
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).
Let's say I have:
ASP.NET Core stand alone Web API project for .NET Core framework
Class Library with EF6 data model for full .NET framework
The ASP.NET Core project refers to the class library
This architecture proposed here:
https://learn.microsoft.com/en-us/aspnet/core/data/entity-framework-6
The question is: will my standalone application be able to execute on the specified target platform (Win, Linux, Mac runtime) after Release (or Publish), if it's dependency targets to full .NET Framework?
Thanks very much
It will be not possible. The same link you provided confirm that:
To use Entity Framework 6, your project has to compile against .NET Framework, as Entity Framework 6 does not support .NET Core. If you need cross-platform features you will need to upgrade to Entity Framework Core.
You can use ASP.NET Core upon .NET Framework (Not .NET CORE) and EF6 (But not cross-platform). But not ASP.NET Core upon .NET Core and use EF6. You will need to use EF Core for that project.
Disclaimer: I'm the owner of the project Entity Framework Classic
That's not possible directly Entity Framework as #Adailson answered
However, it's possible via EF Classic: http://entityframework-classic.net/
That's an EF6 fork that also supports .NET Core. We plan to integrate a ton of features & bug fix.
A community (FREE) and enterprise version (PAID) is available.
What's EF Classic
Entity Framework Classic is a supported version from the latest EF6 code base. It supports .NET Framework and .NET Core and overcomes some EF limitations by adding tons of must-haves built-in features.