Visual Studio 2012 support

[sachinnagawade]

Entity Framework 7 should support Visual Studio 2012 along with Tooling support. All users can not upgrade to VS 2013 immediately. This will also help increase EF7 user base sooner.

[ErikEJ]

Parts of EF requires .NET 4.5.1, so not sure it is a good idea. And a newer VS version "14" is already in the pipeline...

[sachinnagawade]

VS 2012 supports 4.5.1. Here is a link. To increase userbase of EF7, you should seriously think about VS 2012 also. All users can not upgrade VS versions so fast.
http://blogs.msdn.com/b/dotnet/archive/2013/12/09/the-net-framework-4-5-1-is-now-available-on-windows-update-and-wsus.aspx

[bricelam]

Our only real requirements are .NET 4.5.1 and NuGet 2.8.3. If you have these, EF7 should "just work" on VS 2012. What specific errors are you seeing?

[sachinnagawade]

I am not talking about errors but about tooling support. E.g. generating code from existing DB etc. I did not found any such option for VS 2012. This is a feature request. I did not found any option to mark the entry as Feature Request ???

Sent from Windows Mail

From: Brice Lambson
Sent: ‎Friday‎, ‎November‎ ‎7‎, ‎2014 ‎4‎:‎37‎ ‎AM
To: aspnet/EntityFramework
Cc: Sachin

Our only real requirements are .NET 4.5.1 and NuGet 2.8.3. If you have these, EF7 should "just work" on VS 2012. What specific errors are you seeing?

—
Reply to this email directly or view it on GitHub.

[bricelam]

Aside from the Migrations commands, there is currently no tooling for EF7. The work item for reverse engineering is #830

[rowanmiller]

We spent some time discussing this, we'll have support for VS2013 but we probably won't go as far back as VS2012 for officially supported tooling. That said, we are looking at a command line alternative to all tooling, so that would work independent of VS version.

The reason we don't support all past versions is just a cost/benefit thing and we typically support the current and previous release. For EF6.x that is 2013 and 2012 and for EF7 it will be 2015 and 2013.