Devart Forums

Hi,

in this post (viewtopic.php?f=1&t=39716&p=142420&hili ... rd#p142420) it is written that DotConnect for Oracle supports .NET Standard 2.0 and Full Framework again. Thats great but it is also written that we can find the assembly for .NET Standard in the subfolder \Entity\EFCore3. Thats nice but we also need the assembly in the Nuget package (https://www.nuget.org/packages/Devart.D ... e/9.11.951)

In the Nuget Package there is a target .NET Standard 2.0 but with a dependency to Microsoft.EntityFrameworkCore.Relational (>= 2.2.6 && < 3.0.0) and not like in target .NET Standard 2.1 with a dependency to Microsoft.EntityFrameworkCore.Relational (>= 3.1.1 && < 3.2.0).

.NETStandard 1.3
Devart.Data.Oracle (>= 9.11.951)
Microsoft.EntityFrameworkCore (>= 1.1.5 && < 2.0.0)
Microsoft.EntityFrameworkCore.Relational (>= 1.1.5 && < 2.0.0)
Microsoft.NETCore.Portable.Compatibility (>= 1.0.1)
NETStandard.Library (>= 1.6.1)
System.ComponentModel (>= 4.3.0)
System.ComponentModel.Annotations (>= 4.3.0)
System.ComponentModel.Primitives (>= 4.3.0)
System.ComponentModel.TypeConverter (>= 4.3.0)
System.Diagnostics.FileVersionInfo (>= 4.3.0)
System.Reflection (>= 4.3.0)
System.Reflection.TypeExtensions (>= 4.3.0)
System.Xml.XmlDocument (>= 4.3.0)
.NETStandard 2.0
Devart.Data.Oracle (>= 9.11.951)
Microsoft.EntityFrameworkCore.Relational (>= 2.2.6 && < 3.0.0)
.NETStandard 2.1
Devart.Data.Oracle (>= 9.11.951)
Microsoft.EntityFrameworkCore.Relational (>= 3.1.1 && < 3.2.0)

It would be great if you can fix this so can I use DotConnect with EF Core 3.2 under .NET Standard 2.0 (Full Framework).

Full Framework

Thats great but it is also written that we can find the assembly for .NET Standard in the subfolder \Entity\EFCore3. Thats nice but we also need the assembly in the Nuget package

There are only full .NET Framework assemblies in the subfolder \Entity\EFCore3. You should install Microsoft.EntityFrameworkCore.Relational v3.1.1 via NuGet and add the references to your project:
* "C:\Program Files (x86)\Devart\dotConnect\Oracle\Devart.Data.dll"
* "C:\Program Files (x86)\Devart\dotConnect\Oracle\Devart.Data.Oracle.dll"
* "C:\Program Files (x86)\Devart\dotConnect\Oracle\Entity\EFCore3\Devart.Data.Oracle.Entity.EFCore.dll"

Until now I only reference the Nuget Package 9.6.696 (https://www.nuget.org/packages/Devart.D ... re/9.6.696) with EF Core 2.XXXX and it works only with referencing this Nuget Packge. Great experience!

I want the exact behaviour for the new version of DotConnect - only reference the NUGET Package. I don't want install DotConnect for Oracle on all machines - this is not possible in our project/environments.

Please change the existing Nuget Package so that the Nuget Package also targets .NET Standard 2.0 (Full Framework) with EF Core 3.XXX so that we have again a great Nuget experience. Manual referencing dlls to libs is not a great dev experience and is for us no solution.

If you have further questions please let me know.

Shalex wrote: ↑Tue 25 Feb 2020 17:04

Full Framework

Thats great but it is also written that we can find the assembly for .NET Standard in the subfolder \Entity\EFCore3. Thats nice but we also need the assembly in the Nuget package

There are only full .NET Framework assemblies in the subfolder \Entity\EFCore3. You should install Microsoft.EntityFrameworkCore.Relational v3.1.1 via NuGet and add the references to your project:
* "C:\Program Files (x86)\Devart\dotConnect\Oracle\Devart.Data.dll"
* "C:\Program Files (x86)\Devart\dotConnect\Oracle\Devart.Data.Oracle.dll"
* "C:\Program Files (x86)\Devart\dotConnect\Oracle\Entity\EFCore3\Devart.Data.Oracle.Entity.EFCore.dll"

@Shalex Do you have any news for us?

EF Core 3.0 was released for .NET Standard 2.1: https://www.nuget.org/packages/Microsof ... onal/3.0.0. We provided the corresponding assembly and included it in our NuGet package with assemblies for EF Core 1.x, 2.x, and 3.x.

EF Core 3.1 was released for .NET Standard 2.0: https://www.nuget.org/packages/Microsof ... onal/3.1.0. And we decided to preserve support for EF Core 2.x in our NuGet package not to force all our users to migrate to EF Core 3: https://docs.microsoft.com/en-us/ef/cor ... ng-changes.

For .NET Framework users, the provider installation creates EF Core 3 assemblies in the folder of the installation.

In the future, .NET Core 2.x users should decide either to upgrade to .NET Core 3.x or to use .NET Framework assemblies from the installation.

Shalex wrote: ↑Mon 02 Mar 2020 16:00 EF Core 3.0 was released for .NET Standard 2.1: https://www.nuget.org/packages/Microsof ... onal/3.0.0. We provided the corresponding assembly and included it in our NuGet package with assemblies for EF Core 1.x, 2.x, and 3.x.

EF Core 3.1 was released for .NET Standard 2.0: https://www.nuget.org/packages/Microsof ... onal/3.1.0. And we decided to preserve support for EF Core 2.x in our NuGet package not to force all our users to migrate to EF Core 3: https://docs.microsoft.com/en-us/ef/cor ... ng-changes.

For .NET Framework users, the provider installation creates EF Core 3 assemblies in the folder of the installation.

In the future, .NET Core 2.x users should decide either to upgrade to .NET Core 3.x or to use .NET Framework assemblies from the installation.

With this strategy .NET Standard 2.0 (Full Framework) users are locked to EF Core 2.x when you consume the package via Nuget. The EF Core team reverted their decision that EF Core 3.x supports only .NET Standard 2.1 because the .NET world was not ready for .NET Standard 2.1. Now EF Core 3.x supports .NET Standard 2.0 and with this change EF Core 3.x also supports Full Framework.

The newest version of DotConnect for Oracle now supports .NET Standard 2.0 but only with EF Core 2.x. This is different to the strategy of EF Core. It would be great that DotConnect for Oracle have the same strategy like EF Core, supporting .NET Standard 2.0 with EF Core 3.x via NUGET. Please adapt your Devart strategy based on the official strategy of EF Core.

I totally agree, it's very problematic. DotConnect for Oracle for EF Core 3.x should support .NET Standard 2.0.

Hi same for me, it should be really nice to have it more easy to setup for net standard 2.0.
And what about Entity Developer? Why it's impossible to chose EF3.x for net standard 2.0?
Please think about it

michael1988 wrote: ↑Tue 03 Mar 2020 14:17.NET Standard 2.0 users are locked to EF Core 2.x when you consume the package via Nuget

Taking into account users' requests and expected EF Core 5 release, we decided to reopen the ticket and analyze the case again.

Any news?
We need it also in our projects!

The investigation is in progress. As soon as we have any results, we will notify you.

We are currently blocked for months in our transition. Please notify us, if you know the hopefully adapted strategy.

dotConnect for Oracle v9.14 includes the new features:

• Entity Framework Core 5.0 is supported
• Entity Framework Core 3.1.10 is supported
• The behavior is changed: EF Core 3 assemblies available via NuGet package are compiled for .NET Standard 2.0 instead of .NET Standard 2.1
• The behavior is changed: EF Core 2 assemblies are no longer available via NuGet package but created in the provider installation folder

Refer to viewtopic.php?f=1&t=44277 and https://blog.devart.com/entity-framewor ... iders.html.

To work with EF Core 3.1.10, the Target framework of your project with the model should be one of these:
* .NET Core 2.x
* .NET Standard 2.0
* .NET Framework 4.6.1 or higher
After you downgrade the Target framework of your project, you should reload the project.

You make it gripping until the end. Seriously, thanks for the behavior/strategy changes you made. We will have a look at the new nuget packages in the next weeks.

Thanks again, now we can move forward.