• Entity Framework Design

    Model Defined Functions

    Today the Entity Framework, and more specifically the Entity Data Model, have a limited notion of Functions. We are currently restricted to Function Imports that allow stored procedures to be invoked, and Canonical / Store Functions for database independent...
  • Entity Framework Design


    Unfortunately in the current version of the Entity Framework, which ships in .NET 3.5 SP1, we don't make any attempt to Singularize or Pluralize names when reverse engineering a model from the database. So if, for example, your database has a table...
  • Entity Framework Design

    N-Tier Improvements for Entity Framework

    The first version of Entity Framework provides convenient ways to load, manipulate and persist objects and relationships. As with many other O/RMs, Entity Framework has a state manager that tracks every change made. Existing objects are typically loaded...
  • Entity Framework Design

    Foreign Keys in the Conceptual and Object Models

    If you are reading this, you have probably heard by now about the so called impedance mismatch between the relational world and the object world – and there are a number of concepts in the relational database that don’t translate easily to corresponding...
  • Entity Framework Design

    EDM and Store functions exposed in LINQ

    In this post Colin Meek and Diego Vega delve into some enhancements we are planning for LINQ to Entities, anyway over to them... Entity Framework v1 customers preferring to write their queries using LINQ often hit a limitation on the range of functions...
  • Entity Framework Design

    Model First

    One of the most painful omissions from the Entity Framework V1 was Model First, which basically means creating a conceptual 'model first' and then deriving a storage model, database and mappings from that. People ask for this scenario all the time...
  • Entity Framework Design

    Structural Annotations - One Pager

    In V1 of the Entity Framework it is possible to annotate a schema using attributes declared in another XSD. However XML attributes are a very limited form of annotation. It would be better if we could annotate using full elements. This is what we...
  • Entity Framework Design

    Discussion about API changes necessary for POCO:

    Evolving an API to support new requirements, like POCO, while maintaining backward compatibility is challenging. The following design discussion from members of the Object Services team illustrates some of the issues and hard calls involved. Have...
  • Entity Framework Design

    Using Stored Procedures to load structured data.

    V1 of the Entity Framework allows you to use stored procedures in two main ways: Mapping Create, Update and Delete entity operations to appropriate stored procedures. Doing a FunctionImport that allows you to return an enumeration of Entities...
  • Entity Framework Design

    Transparent Caching Support in the Entity Framework

    The Entity Framework's provider model makes it possible for it to work over different database's. The idea being that someone, either the database vendor or a third party, can write a provider that allows the Entity Framework to work with that database...
  • Entity Framework Design

    Computed Properties One Pager

    UPDATE: this blog post is out of date. Please review this instead. If you've been paying attention to what the Entity Framework team has been saying. You will remember hearing us talk about using the Entity Data Model (EDM) as a common way of describing...
  • Entity Framework Design

    Initial POCO Design Screencast

    Two guys on the team knocked out this quick screencast of some of the prototype work we've been doing around POCO an the State Manager. It's not a long or in depth screencast, but we're hoping to inspire some additional feedback. If you prefer to download...
  • Entity Framework Design

    Initial POCO Design 1-Pager

    Here is a raw cut and paste for our POCO 1-Pager. We are currently working through the design and have some prototype work going on and we would like to hear your feedback. Note this is the "feature design 1-Pager" not the "implementation design 1-Pager...
  • Entity Framework Design

    Transparency in the design process

    Today marks the first day of engineering for the ADO.NET Entity Framework V2.0. V2 of the product is a combination of a continued investment in our greater data platform vision as well as a focus on new and expanded ORM scenarios. Some of the things that...
Page 2 of 2 (39 items) 12