ADO.NET Entity Framework Update
Microsoft is deepening its investment in the ADO.NET Entity Framework as a critical piece of Microsoft’s Data Platform vision. Based on the need to align with requirements from key internal partners that are building on the Entity Framework, along with the need for a better tool experience, we have decided to ship the ADO.NET Entity Framework and Tools during the first half of 2008 as an update to the Orcas release of the .NET Framework and Visual Studio. We will continue to ship CTPs and Betas of the ADO.NET Entity Framework that align with Orcas throughout the remainder of this year.
Microsoft shipped the first CTP of the ADO.NET Entity Framework in August of 2006. Customers immediately grasped the power of being able to work with their data through a conceptual model, rather than in terms of database schemas optimized around storage concerns like normalization and data partitioning. In February we added the framework into the CTP and Beta 1 builds of the next version of the .NET Framework and Visual Studio codenamed Orcas.
We’ve collected great feedback from you in these early releases, the most significant being that we need better tools to aid in defining a data model and mapping that model to the database. Although we have tools for generating a direct mapping to the storage schema, the real power of the ADO.NET Entity Framework comes in its ability to flexibly map a variety of relational schema representations to a more appropriate conceptual application model. This has reinforced the need to have a graphical designer experience available for the ADO.NET Entity Framework.
At the same time, Microsoft will be leveraging the Entity Data Model in future versions of Microsoft products such as SQL Server. This Data Platform vision enables customers to leverage their investment in a common conceptual entity model across product lines. Stay tuned for announcements starting next week at Mix around new products building on the ADO.NET Entity Framework.
For more information on the ADO.NET Entity Framework and Microsoft’s Data Access Vision, see the Microsoft Data Access Strategy post on the Data blog.
Mike Pizzo
Architect, Data Programmabilty
Comments
Anonymous
April 28, 2007
So the EDM mapper will now be a part of this release in Half1-2008?Anonymous
April 28, 2007
The comment has been removedAnonymous
April 28, 2007
I wonder if Linq for SQL make it in Orcas? If it does then perhaps the ADO.NET Entity Framework will be ignored. IMHO the fact that there appears to be two different ORM techniques in the Orcas+ timeframe just demonstrates a lack of internal communications around this space.Anonymous
April 28, 2007
First, read the announcement here . Had that deja-vu yet? Me too . But let's not get into that rightAnonymous
April 28, 2007
LINQ for SQL and ADO.NET Entity Framework are not the same things, and I think LINQ for SQL is an convenient for EDM. But I also wonder if LINQ for SQL will appear in the first Visual Studio Orcas RTM.Anonymous
April 28, 2007
According to ADO.Net Team announcement earlier today, the ADO.Net Entity Framework will not ship withAnonymous
April 29, 2007
Here's a suggestion, use EntitySpaces, You could have your application up and running in the same time it takes just to download the Orcas Beta. http://www.entityspaces.net Oh, and we are truly database independent, our NUnit test suite (same physical executable) runs against Microsoft SQL, Oracle, MySQL, Access, and VistaDB. We also support the Compact Framework and run under Medium Trust. We have a tiny footprint, around 150k. Our Dynamic Query API is very nice, who needs LINQ? You can switch from DynamicSQL to StoredProcedures for your CRUD operations at runtime. EntitySpaces uses NO REFLECTION. We also provide the best ADO.NET transaction management for pure ADO.NET connection based transaction via esTransactionScope.Anonymous
April 29, 2007
As many reported ( including me ), ADO.NET team decided to postpone the EDM designer after Orcas/.NETAnonymous
April 29, 2007
ADO.NET Entity Framework UpdateRight on the heals of the .NET Framework 3.5 Beta 1 release comes...Anonymous
April 29, 2007
Microsoft has just announced that the ADO.NET Entity Framework will not be shipped with Orcas (VisualAnonymous
April 29, 2007
Microsoft has just announced that the ADO.NET Entity Framework will not be shipped with Orcas (VisualAnonymous
April 29, 2007
Today the ADO.NET team announced that the ADO.NET Entity Framework will not ship with Visual Studio OrcasAnonymous
April 29, 2007
The comment has been removedAnonymous
April 29, 2007
True, if a “conceptual model first” approach means that I need to wait even longer than the suggested first half of 2008 I’d be happy too!Anonymous
April 29, 2007
Kevin Miller recently blogged about the recent confirmation that the EDM Designer will not be in OrcasAnonymous
April 29, 2007
OK If ado.net entity framework is not supported in Orcas then What is the new thing in .Net Framework 3.5. Doesn't .net framework 3.0 should be enough for Orcas. I am Really Confused With this stupid Strategy.Anonymous
April 29, 2007
Does that mean the terrorsists have won? Don't let the EF go the way of ObjectSpaces. I'm of the opinion that a less than perfect version 1.0 right now is better than a perfect beta version that's always in the future.Anonymous
April 29, 2007
I apologize for the “PR-spin” feel people have associated with this post. Even a short delay of the Entity Framework is a difficult message, especially to convey through the imprecise nature of written communication. How do we convey that we believe this to be the right decision, without people losing confidence in the technology, particularly in light of Microsoft’s less-than-perfect record in shipping ORM solutions, and in the wake of WinFS? I struggled with the wording. With the approach. With the message. Yes, marketing was involved in reviewing the content (of course). I regret now accepting some of their input, but the message is the same. The Entity Framework will not ship in Orcas. It will ship shortly there-after. The slip isn’t about Microsoft’s lack of commitment to the technology. It does give us more time to address some key feedback we’ve received to date from internal and external customers, including providing at least CTP-quality tools for defining flexible mapping between the store and the objects. There’s no way I can convince you that this isn’t another ObjectSpaces, or another WinFS. You’ll have to look at how we continue to deliver over the next few months. You’ll have to look at the quality of the bits. You’ll have to look at the other investments Microsoft is making around the Entity Data Platform, including announcements and demos this week at Mix. This year I celebrate my 20th year at Microsoft. In that time I’ve seen Microsoft invests heavily in a number of technologies that, for one reason or another, never come to market. This isn’t one of them. Michael Pizzo Architect, Data ProgrammabilityAnonymous
April 29, 2007
I guess my question would be what's the rush with Orcas? If EDM needs a bit more time, why not just wait until it's done to ship Orcas? A few more months won't make much of a difference in the long run. Or an alternative idea: since Orcas can target multiple version of the framework, why not just ship Orcas but withhold .Net 3.5 until EDM is ready? That way people who need .Net 3.0 and Vista support can get down to business and we can be spared yet another variation of the framework. Updating VS with an out-of-band enchancement isn't really a problem for me, but the idea of having to put another dependency on clients' machines leaves me unenthusiastic to say the least. I'm sorry if these are all things you've considered before coming to this decision, but the post is so vague I'm having trouble seeing why this was the right way to go. Frankly, I would like to see less input from marketing in the future (aside from making sure nothing gets leaked before it's supposed to and so forth).Anonymous
April 29, 2007
I agree with Bryan. I see no reason to rush out the release of Orcas without EDM. Microsoft has already released a whole lot of products as of recent that I still find myself catching up on. I'm sure the other pieces wouldn't hurt to have an extension of six months either. With that said, although there are many improvements with Orcas, the Entity Framework is the only reason I can see us upgrading.Anonymous
April 29, 2007
Hi Michael I really hope you are right. Please don't let it be a new WinFX/ObjectSpaces. Please, Please, Please. Next... if you realy do this to re engineer the Entity Framwork to support a more POCO/TDD way of developing this is great news. But does this mean that we will see a .NET 3.6 that contains the Entity Framework? I hope not. It would be great if the Entity Framework could be distributed as a bundle of assemblies with our Custom applications (you know... the way that all 3. party assemblies are distributed ;-). That way we could start distribute Beta versions the Entity Framework assemblies as soon as .NET 3.5 ships, and upgrade to RTM when the time comes.Anonymous
April 29, 2007
I almost can't believe the great news that came from MS today. That's right, the ADO.NET EntityAnonymous
April 29, 2007
I almost can't believe the great news that came from MS today. That's right, the ADO.NET EntityAnonymous
April 29, 2007
The comment has been removedAnonymous
April 29, 2007
So I arrived at earlier today and dove pretty much staight into the gestalt of Mix. Registration wasAnonymous
April 29, 2007
@Evan: if you think they'll re-architect the whole stack to do Model first now you're mistaken. They had a looooooooong time to get things done properly. If you think they just need 3-4 more months to make a completely new stack, please explain to me why they needed all these years to come up with a non-model first stack in the first place.Anonymous
April 29, 2007
The comment has been removedAnonymous
April 29, 2007
It is the correct dissension, even if the kids here do not like it :-) If a features needs to be removed from the next VS.NET in order for it to ship, it needs to be removed, I want to use the new WCF and WPF designers in VS.NET, I want to use the new improvements, the entity framework can come later, not a problem, I am interested, but I am not planning to use it in the near future, maybe I am wrong, but it looks to me like a tool for kids who don’t want to learn SQL ;-)Anonymous
April 30, 2007
GT: I'd characterize LINQ to SQL and LINQ to Entities more as tools for people who know SQL, and are tired of re-writing the entire DAL all the time. :)Anonymous
April 30, 2007
"Project Jasper" might be one of the reasons that the Entity Framework slipped past the Orcas RTM timeframe. See http://oakleafblog.blogspot.com/2007/04/to-deliver-dynamic-adonet-30.html. --rjAnonymous
April 30, 2007
To avoid rewriting the data access layer each time, I am using Xsl inside C# to build more C# code, like the C++ template but much better, here is an example with the source code http://web.livetechnologies.ca/Downloads/CsXslInline.zipAnonymous
April 30, 2007
The comment has been removedAnonymous
May 01, 2007
While yesterday was a pretty quiet day at the MEDC, next door at MIX07 things were certainly happening.Anonymous
May 02, 2007
I have a suggestion form Microsoft: BUY NHibernate and Code Smith and solve the problem.Anonymous
May 03, 2007
2007年2月28日，Microsoft 負責資料處理技術之架構師 Mike Pizzo 於他的 blog 中透露了目前 ADO.NET Entity Framework 最新現況。Mike PizzoAnonymous
May 05, 2007
ADO.NET vNext выйдет в 2008г. отдельно от VS OrcasAnonymous
May 09, 2007
The comment has been removedAnonymous
May 11, 2007
Microsoft decided to launch ADO.NET Entity Framework and Tools during the first half of 2008 as an updateAnonymous
May 11, 2007
What are you branding this as .NET 4.0!Anonymous
May 12, 2007
My decision to use DevExpress XPO or ADO.NET Entity Framework for my for my latest project just got a lot easier :-/ Good luck with the '08 release it sounds like you're decided to raise the bar with the delay, but it's frustrating nonetheless! To folks questioning an Orcas release without ADO.NET EF, I'd say folks targeting .NET 3.0 today need Orcas yesterday :)Anonymous
May 13, 2007
I agree with Bryan and Corey. If EDM needs more time, then delay Orcas. My company is still upgrading to VS2005, and many associates are still using VS2003. Release a better, more complete Orcas by delaying it until all is ready.Anonymous
May 13, 2007
@Oidon, No dont hold off the release just for Entity spaces for Orcas, the xtensions to c# and LINQ more than justifies a new release for the next few months. As a lot of comments here suggest there are already many non microsoft alternatives to entity spaces which are ready now (Paul Wilson's OR Mapper, LLBLGEN, Nhibernate, Entity Spaces to suggest a few). But there are not that many (any?) alternatives to something so cool as LINQ.Anonymous
May 13, 2007
Мабуть вже всі чули про то те що ADO.NET Entity Framework не буде в Visual Studio "Orcas"? СоьогодніAnonymous
May 16, 2007
Personally I don't see why some of this stuff isn't released incrementally, the idea of getting some of the functionality in Orcas and the rest letter seemed fine to me.Anonymous
May 23, 2007
This topic came up on an internal mailing list at Microsoft. The question is, will LINQ be usable withAnonymous
June 11, 2007
I just read a post from Mike Pizzo from the ADO.NET team where he announced that ADO.NET EF is pushedAnonymous
June 28, 2007
The comment has been removedAnonymous
July 19, 2007
Entity Framework cut. Positive sign?Anonymous
July 19, 2007
2007年4月28日，Microsoft 負責資料處理技術之架構師 Mike Pizzo 於他的 blog 中透露了目前 ADO.NET Entity Framework 最新現況。Mike PizzoAnonymous
August 28, 2007
So what's the story today (Aug 28, 2007) about ORM. Where today is the BEST tool for doing ORM (Object Role Modelling) that will automatically create the DDL for creating the corresponding database. I've downloaded NORMA but now learn that I need at least "Visual Studio 2005 Standard" for the NORMA tools. Conceptual Modelling (Object Role Modelling) makes sense to me as I envision laying out the design of a project for a customer who knows THEIR domain well but not what an E/R diagram is. thanks - JohnAnonymous
September 04, 2007
I've been working on an open source project you might find interesting: http://www.codeplex.com/nbusiness It's essentially a business object code generator that takes some new approaches to the problem including a C#-esque language to define your entities. One interesting aspect is the strategy of ROM (relational object mapping) vs. ORM. With NBusiness the ideal way of working you would (but certainly do not have to) generate a database off of your definitions rather than vice versa. Of course it is a fully templated code generator and integrated into visual studio! I'd love to hear some feedback. (Is there a better way to communicate with the team than these comments?)Anonymous
December 17, 2007
when ADO.NET Entity Framework RTM to release?Anonymous
January 31, 2008
Microsoft has dropped the Entity Framework , which includes LINQ for Entities, from the .NET 3.5 andAnonymous
May 15, 2008
I am developing a multi language web site using asp.net, linq to entities (or perhaps linq to sql). I have to handle some data in a multi lingual manner. For example I have a News entity in the conceptual model and I'd like to map it to (News, NewsLocal pair) tables in such a way to be able to do following things:
- News n = News.CreateNews(id21, "en-US"); a. n.CreatedOn = DateTime.Now; // must go to News.CreatedOn field b. n.ValidTo = n.CreatedOn.AddDays(7); c. n.Title = "News Test Title"; // must go to NewsLocal.Title field d. n.Body = "News Test Body"; e. db.AddToNews(n); f. db.SaveChanges();
- var q = from n db.News where n.CultureId == "en-US" && n.ValidTo <= DateTime.Now select n;
- Some similar approach for update and delete … Any solution, advice or alternative is needed and welcomed! Following are table creation scripts: USE [ECMS] GO /****** Object: Table [dbo].[News] Script Date: 05/16/2008 13:23:04 / SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[News]( [Id] varchar COLLATE SQL_Latin1_General_CP1256_CI_AS NOT NULL, [CreatedOn] [datetime] NULL, [ValidTo] [datetime] NULL, CONSTRAINT [PK_News] PRIMARY KEY CLUSTERED ( [Id] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO SET ANSI_PADDING OFF USE [ECMS] GO / Object: Table [dbo].[NewsLocal] Script Date: 05/16/2008 13:24:04 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[NewsLocal]( [NewsId] varchar COLLATE SQL_Latin1_General_CP1256_CI_AS NOT NULL, [CultureId] varchar COLLATE SQL_Latin1_General_CP1256_CI_AS NOT NULL, [Title] varchar COLLATE SQL_Latin1_General_CP1256_CI_AS NULL, [Body] varchar COLLATE SQL_Latin1_General_CP1256_CI_AS NULL, CONSTRAINT [PK_NewsLocal] PRIMARY KEY CLUSTERED ( [NewsId] ASC, [CultureId] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO SET ANSI_PADDING OFF GO ALTER TABLE [dbo].[NewsLocal] WITH CHECK ADD CONSTRAINT [FK_NewsLocal_News] FOREIGN KEY([NewsId]) REFERENCES [dbo].[News] ([Id]) ON UPDATE CASCADE ON DELETE CASCADE GO ALTER TABLE [dbo].[NewsLocal] CHECK CONSTRAINT [FK_NewsLocal_News]
Anonymous
July 02, 2008
very helpfully article. i like itAnonymous
September 21, 2008
Keep an eye on these Microsoft .NET technologiesAnonymous
November 19, 2008
I am developing for smart device with windows CE, can i use ADO.NET Entity Framework??Anonymous
December 08, 2008
I am using EF for a 3-tier application, using WCF. I just found that when I change a collection on the client, then the entity cannot be deserialized at the server side. Could somebady explain why is this happenning?Anonymous
August 17, 2009
Re: "using EF for a 3-tier application"... The n-tier Entity Framework collection usage is one of the major Entity Framework limitations in the current version (as of Aug/2009). I worked on one 3-tier project ... then eventually had to switch to nHibernate because of this issue... Apparently in 2010 there will be a new version of the Entity Framework with proper support of n-tier development ...Anonymous
April 05, 2010
I'm encountering some strange behavior and was hoping someone could be point me in the right direction. My setup is as follows: -using EF4/VS2010/.Net4.0 -and using POCO templates with Dynamic Proxies turned OFF
- using dynamic linq to pull my data the problem I'm having is - when I try to save an entity, every other time I save I get an OptimisticConcurrencyException. I don't get this error with the change tracking proxy turned on, but unfortunately I cannot keep it on. if anyone has any ideas I'd appreciate it , I'm pretty stuck right now.
Anonymous
April 05, 2010
Can ignore last post - I was able to get this working...thanksAnonymous
October 15, 2010
The comment has been removedAnonymous
August 04, 2011
How can i access to diferent data sources, especifically 2 diferent databases using entity framework??