Is there a way to use EF with SQL Compact database on the new .NET 5 Windows Framework?
I tried it, but I couldn't make it workable.
Is this library supported in .NET 5?
EntityFrameworkCore.SqlServerCompact40 (looks empty the package folder)
I cannot access to the optionsBuilder.UseSqlCe(#"Data Source=C:\data\Blogging.sdf"); method.
If it is not supported, can I use EF with CE in .NET Core 3.1?
The library only supports EF Core 2.2.
If I get a sponsor I am willing to update.
You can use SQLCE with raw ADO.NET and .NET 5.
See more info here; https://erikej.github.io/sqlce/2020/08/17/netcore-sql-compact.html
What is the latest recommendation for introducing Identity into your existing .NET Core 3.1 WebApi project using EF Core 3.1 DB First approach ?
So after you scaffold database to create your objects in .net project, how do properly "insert" Identity tables ?
The best solution I could find on this topic is an old SO post from almost 5y ago, so I'm wandering is there a new solution to this ?
Using Asp.Net Identity DataBase first approach
thanks
I have used NCache tagetting .net framework 4.6.1 but wanted to convert the same to the .net core 3.0. So, is that possible?
I don't believe it works with Entity Framework 3.0 as Microsoft have changed a lot of things under-the-hood. I've tried upgrading our .Net Core 2.2 project, but NCache was complaining about quite a few things.
Entity Framework Core does not support spatial data, which I need to use in my app.
Can I use Entity Framework 6 in .net core? If so, how can I register DatabaseContext in Startup.cs?
Update
You can now use EF 6.3 with .NET Core 3.0:
https://devblogs.microsoft.com/dotnet/announcing-ef-core-3-0-and-ef-6-3-general-availability/#what-s-new-in-ef-6-3
Below is an excerpt. However, EF Core has come a long way these days and it's worth giving it another go before going back to something that's reaching end-of-life soon. Specifically for your issue, EF Core supports mapping to spatial data types using the NetTopologySuite spatial library since version 2.2.
What’s new in EF 6.3
Support for .NET Core 3.0
The EntityFramework package now targets .NET Standard 2.1 in addition to .NET Framework 4.x.
This means that EF 6.3 is cross-platform and supported on other operating systems besides Windows, like Linux and macOS.
The migrations commands have been rewritten to execute out of process and work with SDK-style projects.
Support for SQL Server HierarchyId.
Improved compatibility with Roslyn and NuGet PackageReference.
Added ef6.exe utility for enabling, adding, scripting, and applying migrations from assemblies. This replaces migrate.exe.
There are certain limitations when using EF 6.3 in .NET Core. For example:
Data providers need to be also ported to .NET Core. We only ported the SQL Server provider, which is included in the EF 6.3 package.
Spatial support won’t be enabled with SQL Server because the spatial types aren’t enabled to work with .NET Core.
Note that this limitation applies to EF 6.3 but not to EF Core 3.0. The latter continues to support spatial using the NetTopologySuite
library.
There’s currently no support for using the EF designer directly on .NET Core or .NET Standard projects.
Original Answer
It isn’t ready yet, but starting with .NET Core 3.0, you will be able to.
https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support-for-windows-desktop-applications/
Similarly, EF6 will be updated to work on .NET Core 3.0, to provide a simple path forward for existing applications using EF6.
https://youtu.be/GN54OV5cCBM?t=1146
But there's also EF6, which we've already announced is going to be ported to work on .NET Core...
UPDATE: Yes, EF6 has been cross-platform since version 6.3. https://devblogs.microsoft.com/dotnet/announcing-ef-core-3-0-and-ef-6-3-general-availability/#what-s-new-in-ef-6-3
ORIGINAL ANSWER THAT IS NOW INVALID: No, you can not directly, because EF6 doesn't support .NET Core.
But, you can create another project, that compiles against full .NET framework and use it as a reference.
MS has actually made a decent tutorial for this:
https://learn.microsoft.com/en-us/aspnet/core/data/entity-framework-6#reference-full-framework-and-ef6-in-the-asp-net-core-project
UPDATE: Yes, EF6 has been cross-platform since version 6.3. https://devblogs.microsoft.com/dotnet/announcing-ef-core-3-0-and-ef-6-3-general-availability/#what-s-new-in-ef-6-3
ORIGINAL ANSWER THAT IS NOW INVALID: Like #Niko said, you cannot directly with EF6 but there is a fork that allows it.
Disclaimer: I'm the owner of the project Entity Framework Classic
Entity Framework Classic is an EF6 fork. It's everything you like about EF6, but with better performance, must-have features, .NET Core support, and more.
There is a FREE Community version that includes pretty much everything and an Enterprise version that include additional features.
Can I use the upcoming Entity Framework 4 with aspnet mvc 2 since mvc is based on 3.5?
If you target .NET 4.0 with your ASP.NET MVC 2.0 Project...you shouldn't have any issues using the new version of Entity Framework.
...or at least I haven't had any issues as of yet.
Sure, you can always create a separate project that will contain the reference to EF4 and then just reference that project from your MVC project. Depending on your architecture, it might be a good idea to separate these concerns anyways.
Also remember, the new versions of the .NET framework are backwards compatible, so any project that needs to reference EF4 should still work with code that needs 3.5.
You can create a mvc 2 with EF v1 with .net framework 3.5