.NET Framework compatibility issue
See original GitHub issueSteps to reproduce
When I try to install the Microsoft.EntityFrameworkCore
NuGet package in my .NET Framework 4.6.2 project, it pulls the whole .NET Standard, which consists of more than 50 additional packages:
The issue
This is obviously wrong, and Microsoft.EntityFrameworkCore
should not pull the NETStandard.Library
when targeting a full .NET Framework.
Further technical details
EF Core version: 1.1.0 Operating system: Windows 10 Pro Visual Studio version: 2015 Update 3
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
Version compatibility in .NET Framework
In practice, this compatibility can be broken by seemingly inconsequential changes in the .NET Framework and changes in programming techniques.
Read more >Introduction to .NET Framework Compatibility - .NET Blog
Quirking refers to the compatibility issue mitigation of having two separate code paths in the .NET Framework and choosing which path to take ......
Read more >NET Framework - Runtime and retargeting changes
Compatibility ensures that each version is additive, so previous versions will continue to work. On the other hand, changes to previous ...
Read more >Troubleshoot blocked .NET Framework installations and ...
The .NET Framework installer cannot run in Program Compatibility mode. To resolve this blocking issue, you must use Registry Editor to ensure ...
Read more >Known issues when you upgrade .NET Framework ...
Find information about application compatibility issues from runtime changes that might affect your app when migrating from . NET Framework 4.6 ...
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 Free
Top 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
It looks fixed to me.
Great!