Does Entityframework 7 support Oracle 12 - entity-framework-core

I am working asp.net 5. I have installed Entityframework 7.
I am not able see code first approach. I have to connect oracle 12g.
Is it that ef 7 is not supporting oracle 12g. Any workaround

There is currently no public information from Oracle about support for EF7 (Ef Core)
There is a issue tracking this here: https://github.com/aspnet/EntityFramework/issues/4293

Related

How to target Oracle 11g instead of 12 for EntityFramework

Im working on a web api project developed with .net entity framework and oracle 11g DB.
Some of the generated statements contain things like "FETCH FIRST 1 ROWS ONLY" which I believe are only supported in Oracle 12. How can I configure the project to tell entity framework that it should generate statements compatible with Oracle 11?

Can Entity Framework 6 be used in a .NET Standard project?

And if not, will it be? If so, when?
I haven't been able to find any clear official information on this, and the limited information I was able to find on Stack Overflow is a year or two old.
I was able to find official information saying EF 6.3 will be able to be used in a .NET Core project, but I couldn't find a release date for it, nor am I sure what the implications for use in a .NET Standard project are.
EF 6 supports .NET Standard 2.1, which is currently supported by .NET Core 3.0 or later - no .NET Framework version. EF 6 also supports .NET 4.0 and 4.5 or later.
https://github.com/aspnet/EntityFramework6/blob/release/6.4/src/EntityFramework/EntityFramework.csproj#L6
Some clarification, since EntityFramework 6.3.0 .NET Standard 2.1 has been supported. However there is no .NET Framework version that supports .NET Standard 2.1. Comment from Microsoft:
NET Framework won't support .NET Standard 2.1 or later versions. For
more details, see the announcement of .NET Standard 2.1.
This means that a majority of all applications using EntityFramework 6.X won't be able to use the .NET Standard 2.1 project anyway.
https://learn.microsoft.com/en-us/dotnet/standard/net-standard
https://www.nuget.org/packages/EntityFramework/#

How to use EF Core (EF7) with Mysql server?

I am developing asp.net 5 (now called ASP.NET Core) on linux. But I cannot connect between EF7 (now called EF Core) and Mysql server. Please tell me any solution that you knew.
Thanks.
All available providers are listed at https://learn.microsoft.com/en-us/ef/core/providers/. At time of writing, there are 3 different EF Core providers, two community versions and one official version.
UPDATE Sept 15, 2016
MySQL released the first version of an official provider for EF Core.
https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore
There is also a community version of a MySQL provider
https://www.nuget.org/packages/Pomelo.EntityFrameworkCore.MySQL
UPDATE May 23, 2016
MySQL has announced (quietly) that they are building an EF Core 1.0 provider. There are no details yet on its availability. See https://docs.efproject.net/en/latest/providers/mysql/index.html
Also, DevArt announced a month ago that their (proprietary, not-free) providers support EF 7 on .NET Framework only, including their MySQL provider. No news yet about their intention to support .NET Core. http://blog.devart.com/entity-framework-core-1-entity-framework-7-support.html
I have good news, guys. Like one said : "Pas le temps de niaiser".
Entity Framework 7 will support soon MySQL, trusting this page from the documentation :
https://docs.efproject.net/en/latest/providers/mysql/index.html#coming-soon

How to launch entity framework project

I am completely unaware of EF, but got an EF project from a candidate. Couldn't open it in Visual Studio 2010 and want at least to run it in IIS to review if neccessary functionality has been done.
How to install it in IIS ?
Entity Framework 6 is not supported by VS 2010, please check that this is not your problem.
Ensure your IIS server has .NET 4 for EF 5 and below, or .NET 4.5 if using EF 6
You will probably also need to edit the supplied connection string to point at a valid database server.

Upgrading from the June CTP EF 4.2

We're currently developing an application that is using EF Code first (EF June 2011 CTP).
My first question is: Is it worth trying to upgrade to use a later version of EF?
Secondly, if so, does anyone know the steps involved to upgrade - when I try to install the NuGet package for EF 5.0 - beta 2, I end up with issues as the target framework is still 4.2.
Many thanks,
James.
The CTP is long time dead with no other version coming because all that stuff is currently part of .NET 4.5 beta and EF 5.0 beta. You must upgrade to those two and the upgrade will consist of re-targeting application back to .NET 4.0 / .NET 4.5, removing all dependencies to your current EF version and re-adding those dependencies for .NET 4.5 / EF 5.0.
Some time ago I wrote a blog post on this: http://blog.3d-logic.com/2012/04/11/entity-framework-zombie-a-k-a-microsoft-entity-framework-june-2011-ctp/. There is a number of issues with CTP 4.2 because of technical challenges related to shipping a .NET Framework library out of the .NET Framework (like 4.2 target). Move to .NET Framework 4.5 that contains the same feature set as EF 4.2 + bug fixes and has a go-live license. Use EF 5.0 on top of it and you will be in a better world.
Thanks for all the responses.
My main issue is that we rely heavily on ENUMs in our implementation of 4.2 code first. I attempted to migrate the project to 4.5 but ENUMs are not supported, and there is also an issue with table per hierarchy (which is easy to fix). The next move will be to upgrade to VS11 and use 5.0 - but this is a big undertaking.
#jwsadler:
Enums are supported by core EF libraries released as part of .net Framework 4.5 (e.g. System.Data.Entity.dll). To make enums work with CodeFirst/DbContext you do need EF 5.0.0 package from NuGet (use Install-Package EntityFramework -pre (-pre is important)). You need VS 11 for this since Visual Studio 2010 cannot be used to create applications that target .NET Framework 4.5. Note that when installing the nuget package on Visual Studio 11 the target version of the .NET Framework set for the project is taken into account. If you target .NET Framework 4 you will not be able to use EF5 features like enums or spatial.