Support for EF Core 3.1 on .NET Standard 2.0
Posted: Thu 10 Sep 2020 14:16
Hi :)
Having looked into things, EF Core 3.0 was only built for .NET Standard 2.1 (.NET Core only), but EF Core 3.1 was then built to be supported on .NET Standard 2.0 (.NET Framework 4.6.1+).
You guys' documentation claims to support EF Core 3.1, but we are facing some odd dependency-graph issues with your NuGet packages, when we are on .NET Framework 4.7.2, using EF Core 3.1 and trying to use your latest dotConnect for Oracle NuGet packages.
In particular, your Devart.Data.Oracle.EFCore version 9.12.1064 (currently latest version on .NET Standard 2.0) has a .NET Standard 2.0 constraint on it that states:
Microsoft.EntityFrameworkCore.Relational (>= 2.2.6 && < 3.0.0)
To us, this doesn't make very much sense, since presumably when using the main package of Microsoft.EntityFrameworkCore 3.1.3 (currently latest supported version according to the dotConnect for Oracle History changelog), the ".Relational" package is enforced to be the same version.
Is it the case that we should be trying to use Microsoft.EntityFrameworkCore 3.1.3 (whatever is supported according to your change logs) but keep the ".Relational" package on the 2.2.6 version? It seems a bit weird at the very least, and we would fear the occurrence of bugs as a result of the version discrepancy, especially when it's a different major version as well.
We figured that perhaps the issue was that you only support EF Core 3.1 on .NET Standard 2.1 (even though it supports .NET Standard 2.0), but at least this page here does not seem to suggest that there are any such constraints: https://blog.devart.com/entity-framewor ... iders.html
Are we misunderstanding or missing something obvious here? :)
Having looked into things, EF Core 3.0 was only built for .NET Standard 2.1 (.NET Core only), but EF Core 3.1 was then built to be supported on .NET Standard 2.0 (.NET Framework 4.6.1+).
You guys' documentation claims to support EF Core 3.1, but we are facing some odd dependency-graph issues with your NuGet packages, when we are on .NET Framework 4.7.2, using EF Core 3.1 and trying to use your latest dotConnect for Oracle NuGet packages.
In particular, your Devart.Data.Oracle.EFCore version 9.12.1064 (currently latest version on .NET Standard 2.0) has a .NET Standard 2.0 constraint on it that states:
Microsoft.EntityFrameworkCore.Relational (>= 2.2.6 && < 3.0.0)
To us, this doesn't make very much sense, since presumably when using the main package of Microsoft.EntityFrameworkCore 3.1.3 (currently latest supported version according to the dotConnect for Oracle History changelog), the ".Relational" package is enforced to be the same version.
Is it the case that we should be trying to use Microsoft.EntityFrameworkCore 3.1.3 (whatever is supported according to your change logs) but keep the ".Relational" package on the 2.2.6 version? It seems a bit weird at the very least, and we would fear the occurrence of bugs as a result of the version discrepancy, especially when it's a different major version as well.
We figured that perhaps the issue was that you only support EF Core 3.1 on .NET Standard 2.1 (even though it supports .NET Standard 2.0), but at least this page here does not seem to suggest that there are any such constraints: https://blog.devart.com/entity-framewor ... iders.html
Are we misunderstanding or missing something obvious here? :)