BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage ADO.NET Entity Framework Content on InfoQ

  • IBM’s Data Server Provider for .NET Supports the Entity Framework

    IBM has released the production version of its Data Server Provider for .NET including support for Microsoft’s Entity Framework allowing its users to create EDM schemas, and to execute EntitySQL and LINQ statements.

  • LINQ to SQL, The Next Step

    Despite the numerous problems with Microsoft ORMs and the plethora of alternatives such as LLBLGen, nHibernate, and OpenAccess, many developers are forced to use Microsoft tech because that is why their company or customer wants. And between the two offerings, it seems most developers believe that Entity Framework is not a viable option. So what are they do to?

  • Does LINQ-to-Entities really return different results depending on previous queries?

    In a recent blog post Stu Smith claimed that “LINQ-to-Entities will return different results depending on what previous queries you’ve executed!”. If true, this would make using Entity Framework much harder than necessary to use. We talked to Elisa Flasko of the ADO.NET Team to find out what’s really going on.

  • Working Around Entity Framework's Large Data Model Issues

    The Entity Framework doesn't support data models with much more than 50 to 100 entities. But since companies typically run everything from one central database, several hundred tables are the norm. Microsoft's ADO.NET team is presenting an article on Working With Large Models In Entity Framework, a list of issues and work-arounds for EF users.

  • Meta-data Synchronization Tools for LINQ to SQL and ADO.NET Entity Framework

    The designers in both LINQ to SQL and ADO.NET Entity Framework have a number of limitations. In order to work around these limitations, products such as Huagati DBML/EDMX Tools have been developed. There is no bloat here, everything is a must have for many shops.

  • No Change Tracking for ADO.NET Entity Framework 2010

    One of the biggest complaints about ADO.NET Entity Framework was that it did not support change tracking. Despite everything from ADO.NET DataSets to every single non-Microsoft ORM having support for this out of the box, Microsoft has no intention of fixing this in the .NET 4.0/VS 2010 timeframe.

  • Is LINQ to SQL Truly Dead?

    Back in July we reported that LINQ to SQL was transferred to the SQL Data Programmability team. This event raised a lot of concern in the developer community, who worried that work on LINQ to SQL would halt in favor of ADO.NET Entity Framework. A recent announcement by Tim Mallalieu, Program Manager of both LINQ to SQL and Entity Framework, has exacerbated those concerns.

  • Should LINQ to SQL Go Open Source

    More and more, LINQ to SQL is being seen as a temporary solution. With the impending release of ADO.NET Entity Framework, a lot of people are worried that development on LINQ to SQL will fall by the wayside. With Microsoft's long history of developing and discarding database access technologies, these concerns are not without merit. So this raises the question, "Should LINQ to SQL Go Open Source?"

  • ADO.NET Entity Framework Taking Some Heat

    A petition has started by the community to express concerns over Microsoft's upcoming release of the ADO.NET Entity Framework. The petition titled "ADO.NET Entity Framework Vote of No Confidence", aims to raise awareness of design and implementation issues foreseen by experts in the industry.

  • Digging into the Performance of the ADO.NET Entity Framework

    The ADO.NET Team recently discussed various performance aspects of the ADO.NET Entity Framework. The ADO.NET Entity Framework entered its third beta back in December and since that time the team has provided developers with information about using the framework but now they are providing developers with the performance aspects.

BT