Skip to Main Content
  • Questions
  • Problems EntityFramework with Oracle.ManagedDataAccess

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Alexis.

Asked: April 10, 2025 - 10:10 pm UTC

Last updated: April 19, 2025 - 1:50 am UTC

Version: 21c

Viewed 1000+ times

You Asked

I created a new project in Visual Studio 2019 with Entity Framework v6.5.1, Oracle.ManagedDataAccess v23.8, and Oracle.ManagedDataAccess.EntityFramework v23.8.
When I add an ADO.NET Entity Data Model, I select EF Designer from the database. It then prompts me for the connection string. I add it, test it, and everything works. When I click Next, a window appears asking me to select the EntityFramework version. The wizard automatically exits and returns me to the first screen to reselect the ADO.NET element. Therefore, it doesn't create the model or the EDMX file.

This doesn't happen when I use Oracle.ManagedDataAccess v19.27 and Oracle.ManagedDataAccess.EntityFramework v19.27.

I can't update to the latest version? Please help.

and Connor said...

I asked Alex Keh and Christian Shay, the PMs for the product:

The major version of Oracle Data Provider for .NET that is referenced in their project must match the major version of Oracle Developer Tools for Visual Studio (ODT) for this to work. So in this case, you must use ODP.NET 19 in their project.

The alternative is to upgrade to Visual Studio 2022 and use ODT version 23.6 with ODP.NET 23.8.

Rating

  (2 ratings)

Comments

Thanks!

Alexis Sifontes Dorta, April 15, 2025 - 5:17 am UTC

I have another project where I updated to version 23.8 and it worked correctly. And it's the same VS2019 environment.

Could there be something extra in that project where the update did work? I looked for differences and couldn't find any.

Thank you very much for the response. I'll keep it in mind, but I still have that concern.

Best regards!
Connor McDonald
April 19, 2025 - 1:50 am UTC

I have another project where I updated to version 23.8 and it worked correctly

I would suspect there's a difference between "it works" and "it works and we support the configuration".

I'll ask around internally, but just because something works doesn't mean its supported.

Thanks!

Alexis Sifontes Dorta, April 19, 2025 - 2:30 am UTC

Thank you for your response and concern about the case, Connor. Best regards.