Entity Framework assemblies out of .NET Framework
A ORM framework needs a much more frequent releases that .net framework
Felipe Fujiy Pessoto
shared this idea
We have been able to release many important features without waiting for .NET 4.5 and VS 11, like Code First, DbContext and Migrations, but some other “deeper” features had to wait. We are working on a solution so that in the future you won’t have to wait so long.
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!
