.NET Core 3.0 and EF Core 3.0.0 support
See original GitHub issueThe EF Core nuget packages needs to be updated to support .NET Core 3.0. When migrating from .NET Core 2.2 to 3.0 and EF Core to 3.0.0 assembly cannot be loaded:
System.TypeLoadException: Method 'get_Info' in type 'EntityFrameworkCore.Cacheable.CacheableOptionsExtension' from assembly 'EntityFrameworkCore.Cacheable, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:6
Top Results From Across the Web
Announcing Entity Framework Core 3.0 and ...
Support for .NET Core 3.0. The EF 6.3 runtime package now targets . · Support for SQL Server hierarchyid · Improved compatibility with...
Read more >Entity Framework Core 3.0: A Foundation for the Future
EF Core 3.0 depends on .NET Standard 2.1 and no longer supports .NET Standard 2.0. This is important to understand because .NET Standard...
Read more >Does EF Core 3.0 do not support .net framework any more?
EF Core 3.0 is based on .NET Standard 2.1 while .NET Framework 4.8 does not have .NET Standard 2.1 support. So you can...
Read more >Microsoft.EntityFrameworkCore 3.0.0
Version Downloads Last updated
8.0.0‑preview.7.23375.4 8,541 11 days ago
8.0.0‑preview.6.23329.4 33,173 a month ago
8.0.0‑preview.5.23280.1 45,524 2 months ago
Read more >NET Core 3.0.0 - September 23, 2019
This release includes .NET Core 3.0.0 and .NET Core SDK 3.0.100. Visual Studio compatibility: .NET Core 3.0.0 requires Visual Studio 2019 16.3 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still a problem with this, I’m looking in implementation.
This is still an issue for .NET Core 3.1