Comments (5)
Hi @mpickers,
We're targeting only net472;net6.0
for the EntityFramework6
package since there is no reason to do otherwise. For the EntityFrameworkCore
package we're targeting net6.0;net7.0;net8.0
just because we're referencing a different major EF version for each of them. As far as the EF6 is concerned, there is no (and will not be) new major version.
If a given library targets net6.0
doesn't mean it can be consumed only by net6.0
projects. It is the minimum required version. The runtime is always backward compatible. So, if you have a net8.0
project and for some reason, you're still using EF6, you won't have any issues referencing the Ardalis.Specification.EntityFramework6
NuGet library.
from specification.
Everything should still work without these, right? I'm still using this package with my net8 apps no problem. If you need it, I'm not opposed to adding it, but what error are you running into?
from specification.
No specific error at this stage, just reviewing packages we use for net8 compatibility (by way of looking at what target frameworks our nuget dependencies target) for what needs attention for migrating from net6 to net8.
I realize the following is a little outside of scope, but I'll put the question out there...
Do you know of a reference anywhere that states that net6 and net7 targeted packages are compatible with later versions of net core?
I have noticed that packages that don't explicitly target net8 still seem to work or nuget at least doesn't balk when adding those packages to a net8 project. However, I haven't been able to find anywhere that states that this is expected
https://learn.microsoft.com/en-au/dotnet/standard/frameworks
My assumption then if this "just works" is that the only reason for targeting a specific framework is to a) Say that it's ok in net core land or b) That it targets a new set of APIs in that net core version.
from specification.
@fiseni do you know of any good reason to add more recent framework targets (or not)?
from specification.
Hi @fiseni,
Greatly appreciate the explanation!
If a given library targets net6.0 doesn't mean it can be consumed only by net6.0 projects. It is the minimum required version. The runtime is always backward compatible.
This is the part I was missing. It's not obvious from the Microsoft release notes/doco. No doubt it's somewhere.
cheers
Mark
from specification.
Related Issues (20)
- Strange behavior when compare DateTime HOT 3
- Apply Distinct in specification query HOT 1
- How to combine specifications? HOT 17
- Implementing additional provider for Azure Storage Tables HOT 1
- Which Design Pattern is behind Evaluators? HOT 1
- Cannot unit test specifications which sort by a Smart enum HOT 2
- Apply Entity and Aggregate Domain-Driven Design approach to Specification and Repository HOT 2
- ardalis.specification.entityframeworkcore is missing NuGet package README file
- Many-to-Many w/ INNER JOIN HOT 1
- System.MissingMethodException: Method not found
- Allow combination of Specification with different projections HOT 6
- InMemory SearchExtension bug HOT 3
- Can ignore properties in Select Specifications? HOT 4
- How to use ExecuteUpdateAsync? HOT 8
- Search in result dto object instead of db class HOT 4
- Make the SaveChangesAsync call optional in RepositoryBaseOfT HOT 8
- Reading as 'System.Object' is not supported for fields having DataTypeName 'public.vector'
- Make repository methods protected to allow for subclassing HOT 2
- Search by value object's Value property: Translation error HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from specification.