StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>My understanding is that EF >= 4.1 (including EF 5) consists of</p> <ul> <li>the EF "core libraries" like (<code>System.Data.Entity.dll</code>) which are part of the .NET Framework</li> <li>the additional package/assembly you can download via Nuget which contains the <code>DbContext</code> API and Code-First development</li> </ul> <p>There were plans and an attempt in summer 2011 (the <a href="http://blogs.msdn.com/b/adonet/archive/2011/06/30/announcing-the-microsoft-entity-framework-june-2011-ctp.aspx" rel="noreferrer">Entity Framework June 2011 CTP</a>) to release the <code>enum</code>, spatial support and other new features (except Code-First Migrations) as an update of the core librares before .NET 4.5 is released. But the EF team has decided that such out-of-band updates are possible for the NuGet package (that's why EF 4.3 already has the Migrations feature that didn't require to touch the core libraries), but for the core libraries they are too difficult and can't be done before .NET 4.5 release:</p> <blockquote> <p>There are two logical parts to the Entity Framework, the core components that ship inside the .NET Framework and Visual Studio and the ‘out of band’ components that we can update on a much more frequent schedule. We are currently looking at how we can update the core components on a more frequent cadence as well. The ‘EF June 2011 CTP’ was our first attempt at shipping the core components more frequently and it’s become clear we’re just not technically ready to do this yet.</p> <p>Core components include:</p> <ul> <li>Core EF Runtime (System.Data.Entity.dll & System.Web.Entity.dll)</li> <li>EF Designer</li> </ul> <p>Out of band components include: (We will likely ship more out of band components in the future)</p> <ul> <li>The DbContext API & Code First (EntityFramework.dll)</li> <li>T4 Templates for using DbContext API with Model First & Database First</li> <li>EF Power Tools</li> <li>Code First Migrations</li> </ul> </blockquote> <p>(Quote from <a href="http://blogs.msdn.com/b/adonet/archive/2011/08/09/ef-releases-amp-versioning-call-for-feedback.aspx" rel="noreferrer">here</a>.)</p> <p>That means that <code>enum</code> support for EF will be part of the .NET 4.5 core libraries and not of the downloadable EF 5 NuGet package. Hence the new EF features like <code>enum</code> and spatial support are not available together with .NET 4.0.</p> <p>More about the history and reason of separating "EF Core libraries" from "EF NuGet package" is here: <a href="http://blogs.msdn.com/b/adonet/archive/2011/10/18/how-we-talk-about-ef-and-its-future-versions.aspx" rel="noreferrer">http://blogs.msdn.com/b/adonet/archive/2011/10/18/how-we-talk-about-ef-and-its-future-versions.aspx</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload