Entity Framework assemblies out of .NET Framework
A ORM framework needs a much more frequent releases that .net framework
EF6 alpha 1 is the first public preview release that includes the EF6 codebase released completely out of band of .NET. See here for the announcement: http://blogs.msdn.com/b/adonet/archive/2012/10/30/ef6-alpha-1-available-on-nuget.aspx
8 comments
-
Paweł
commented
You can't expect customers to buy new Visual Studio every two years. Why can't I get updates to EF (and .NET) and keep using VS 2008? My bosses don't want to listen to me when I say I would like .NET 4 and VS 2010
-
AdminDiego Vega
(Admin, DataFx)
commented
@Oskar, Felipe: This is great feedback. We have indeed looked at this. The June 2011 CTP of EF was a first attempt, and we keep working on it.
-
shimmy
commented
Enums, please
Urgently!! -
Felipe Fujiy Pessoto
commented
The worst isn´t to wait, will be having to install .NET 4.5 to have all new features: http://blogs.msdn.com/b/adonet/archive/2011/10/18/how-we-talk-about-ef-and-its-future-versions.aspx
-
Rudi Larno
commented
Together with semantic versioning and this:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2035455-use-nuget-to-install-most-of-the-componentsthe microsoft development teams and we developers could get our bits out/in faster than the current two-year cylcle of VS.
Mark Rendle also has a great view on this: http://blog.markrendle.net/2011/06/28/how-i-would-like-microsoft-to-distribute-net-v-next/
-
Oskar
commented
I agree, just put it all in a sweet little NuGet package
-
Felipe Fujiy Pessoto
commented
I think that EF should be released as ASP.NET MVC, independent of Framework
-
Ross Mason commented
Please please please don't make us wait for a mapor release to get the TPT SQL generation bug fixed!