Partager via

Entity Framework V2 - Transparency in the design process

  • Article

Today marks the first day of engineering for the ADO.NET Entity Framework V2.0, and the team has been looking at various options to ensure that the design of Entity Framework V2 truly reflects the requirements of the day to day challenges that our developer community faces when building real-world applications and services. We would like to start by being as transparent as possible in our design process.

We will follow a process similar to what you may have seen on Astoria Team blog (ADO.NET Data Services) over the past 9 months, regularly posting our design notes to the New Entity Framework Design blog and providing you with the opportunity to give feedback when we are actively discussing a certain aspect and before we have made a final decision. For more information on how this process will work, check out our first post, and expect more to come very soon!

Elisa Flasko
Program Manager, Data Programmability

Comments

  • Anonymous
    June 23, 2008
    i think this and this is good news: MS takes a second try to make the ADO.NET Entity Framework a really

  • Anonymous
    June 24, 2008
    Many thanks for the work on the Entity Framework. I for one will be using it for all new .NET development projects from now on. It's such a relief to be able to standardise using one framework baked into .NET. And that there is a huge community there and documentation to get up to speed with the framework.

  • Anonymous
    June 25, 2008
    Once think that seems odd to me is the architectural issues of ORM tools. Everywhere else in our code, we encourage loose coupling though inteface-based programming in our layers. With stored procedures, we can have that at the data layer, allowing the DB team to change table layouts and optimize procedures as long as they don't change the "interface" (the stored procedure parameters and return values). With ORM tools, my code again becomes tied to the table structure and field names. Is it just me, or does this seem like a step in the wrong direction?

  • Anonymous
    June 30, 2008
    I’ve been doing my best to do other things lately and completely missed this terrific news. Opening up

  • Anonymous
    July 10, 2008
    Thank you so much for this great tool. If it were an ORM, I'd be very happy. The fact that it is a Entity Framework makes me very very happy. My development efforts just got a whole lot easier. I thank you for providing multiple database support. I thank you for providing a way to query multiple databases (with ease). I thank you for the Linq to entity support. And last but not least I thank you for providing a better way to access data in a object orientated way when using an object orientated programming language. I can't wait for version 2 to see what else you can come up with, but I'm not hanging out for it, because everything I need is pretty much contained within version 1.

  • Anonymous
    August 26, 2008
    I'm 100% with "A very happy user", but I believe I've found a bug in the ADO.NET Entity Framework (.NET 3.5 SP1).  Is there a place where I can post the sample to reproduce it so that it can be discussed?

  • Anonymous
    June 29, 2009
    I noticed someone posted "Thank you for providing multiple database suppport".  Is that support concerning an entity data model having access across multiple databases or servers?  That's what I'm looking for... Does anyone have any resources feedback on that? Thanks, Todd