DotNetKicks.com - Stories tagged with EntityFramework

Entity Framework 4.0: What You May Be Missing

Thu, 25 Jun 2009 03:15:43 GMT

I have listed these articles in chronological order, oldest to newest, start from where you find interesting, or start at the top as it's the first article I could find where EF 4.0 was announced and always good to get that initial background.

Entity Framework 4 Persistence-Ignorance First Look

Thu, 21 May 2009 06:38:09 GMT

Introduction: From the moment I put my hands on Visual Studio.Net 2010 Beta 1 and I'm targeting EF4 -Entity Framework 4- as I was very excited to checkout the new cool feature of it. Here I am going to highlight my first look at Persistence-Ignorance support in EF4.

Introducing DataLoadOptions for Entity Framework ObjectContext

Sun, 17 May 2009 01:11:43 GMT

On my previous post "What about DataLoadOptions for Entity Framework ObjectContext?" I was suggesting another way to define eager loading for Entity Framework. In this post I will introduce my DataLoadOptions for Entity Framework ObjectContext. The beginning: Actually Eager and Lazy loading on Entity Framework is not that much fun like in Linq to Sql. However this is going to be improved in EF4. Here I will focus on eager loading and my slight improvement to define eager loading in Entity Framework.

What about DataLoadOptions for Entity Framework ObjectContext?

Fri, 24 Apr 2009 11:01:31 GMT

I think the proper way to start this post is to ask How do you do eager loading with Entity Framework? And the basic native simple answer is by using ObjectQuery<T>.Include(string) method. No matter what you tried to do, you'll end up using this way. So there was ideas about how enhance the eager loading in our Entity Framework base applications. You can read about some of these ideas....

Stored Procedures that Return Primitive Types in Entity Framework

Fri, 03 Apr 2009 21:41:59 GMT

One drawback of Entity Framework designer is that it does not generate code in the object context for function imports of stored procedures that return a primitive type. This post will explain how to achieve this functionality up until the designer will support it in the next release of Entity Framework.

Entity Framework Mapping Helper

Fri, 03 Apr 2009 20:16:36 GMT

Entity Framework Mapping Helper is a very useful tool that was written by the Entity Framework team and can help you to get started with various of mappings scenarios.

Creating Complex Types in Entity Framework

Fri, 03 Apr 2009 02:26:13 GMT

The following post will explain what are complex types in Entity Framework and how to use them.

DDD & TDD using EF, Part 2.A Unit Testing Entities With Moq3

Wed, 25 Mar 2009 03:26:11 GMT

I had few previous posts about DDD & TDD with Entity Framework that you might need to return to them before you proceed with this post. To summarize these posts, I was trying to build testable Models that is based on EF. But EF doesn't support Persistence Ignorance in its first version which make testing it in most cases require a database connection where you can test you code against it. My target was to build a testable models based on EF and that is independent of any underlying data source.

Domain Driven Design & Test Driven Design\Development with Entity Fram

Wed, 25 Feb 2009 01:42:42 GMT

decided to provide some integration testing before proceeding as a proof of concept. In integration testing I will connect to the database and perform unit testing while connecting to the database.\ This unit test is almost identical to the one in my previous post. Except here I am testing the results that is coming out from EF and Database. My target is to test IDataContext Implemented methods in NorthwindDataContext

DDD & TDD with Entity Framework, Part 1.a Refactoring & Unit Testing

Wed, 11 Feb 2009 07:03:11 GMT

In previous post I talked about building domain model for Northwind using Entity Framework. I used the generated ObjectContext class which is NorthwindDataContext as the basic Data Access Layer Helper. But my NorthwindDataContext is implementing custom interface I created in order to be able to make my Data Access Layer testable as well as to be independent from EF. My target is to achieve decoupling between EF and all layers above it. This include Repository classes. This might not be of a big benefit to everyone, because my repositories implementation will still dependent on IDataContext. But for me it will help to do TDD more smoothly regardless of my underlying data access layer. Beside it might allow me in future to be able to switch from EF to LINQ to SQL and just implement my IDataContext interface for LINQ to SQL.

Domain Driven Design & Test Driven Design With Entity Framework, Part

Thu, 05 Feb 2009 08:44:31 GMT

In my previous post I talked about definitions of TDD as specified in different sources. Here in this post I'll walk-through applied Domain Driven Design & Test Driven Design on Entity Framework. I assume that you already know Entity Framework and how to create your entity data modes using Visual Studio.Net 2008 with SP1.

Making the Entity Framework Fit Your Domain - Part 1

Wed, 31 Dec 2008 00:16:04 GMT

Need to use the Entity Framework but don't know how to fit it into your domain? Come check out this series on CodeThinked.com where you will learn how to keep your domain entities fairly clean while using the Entity Framework.

Learning Entity Framework

Thu, 25 Dec 2008 17:05:47 GMT

I suppose you have already heard about the Entity Framework, but probably didn't have a chance to try it in action. So, you want to learn it. Of course, you can start with MSDN that is indeed is the number one resource .NET developers, you can also find a dozen of tutorials on the Net, but you know it's always pleasant to have a paper book or perhaps its electronic versions that you can read everywhere, not only in front of your computer.

Book Review: Entity Framework Tutorial

Sun, 21 Dec 2008 00:15:31 GMT

Entity Framework Tutorial Book Review

New Entity Framework / LINQ blog!

Fri, 12 Dec 2008 13:50:24 GMT

Just a quick recommendation note: One of my colleagues, Julien Hanssens, has started blogging on his experiences with the Entity Framework and LINQ. Here are some links to get you started

Free Entity Framework Learning Guide

Sun, 07 Dec 2008 13:01:02 GMT

Zeeshan Hirani presented this free EF guide too EF community. You can download this guide in PDF format.

LINQ Method cannot be translated into a store expression.

Tue, 18 Nov 2008 18:53:13 GMT

A short snippet/workaround if you ever see the following exception: LINQ to Entities does not recognize the method ... , and this method cannot be translated into a store expression. It is thrown because in the Entity Framework Custom Methods & Extension Methods cannot be translated into a store expression.

LINQ to XML - XPath

Mon, 10 Nov 2008 17:24:02 GMT

LINQ to SQL may be on it's way out, but LINQ is no way out at all! And don't worry about LINQ to SQL, the ADO.NET Entity Framework is available and guess what it's awesome. Another good usage for LINQ is when you need to query an XML file. When working with LINQ to XML you may remember the old days when you used XPath. But don't worry anymore there is support for XPath on LINQ to XML. There are extension methods for LINQ to XML in the System.Xml.Xpath namespace! Read this blog post if you are interested in an example, and find out if there are any performance issues! Have fun reading!

Inheritance and Associations with Entity Framework Part 3

Thu, 02 Oct 2008 03:57:11 GMT

On part 1 and part 2 I explored how to apply 2 different inheritance models (TPH & TPT) in Entity Framework. In this part I'm going to demonstrate associations between 2 base entities. And how to filter end properties to return specific type (sub entity).

Inheritance and Associations with Entity Framework Part 2

Mon, 29 Sep 2008 18:28:09 GMT

In the previous part I discussed Table-per-Hierarchy Inheritance, in this part I'll go through Table-per-Type Inheritance model. There is a video demonstrating this model if you wish to watch. Here I'll update my previous sample with new entities that demonstrate the Table-per-Type Inheritance model

Inheritance and Associations with Entity Framework Part 1

Wed, 24 Sep 2008 23:53:01 GMT

In this multi parts series I'll explore how to build inheritance with Entity Framework showing 2 different approaches of inheritance in Entity Framework. Beside that I'll show how to build simple association between 2 entities and show how to provide custom code to retrieve other parts of the relation when inheritance is applied. In this part I'm exploring Table-per-Hierarchy Inheritance model in EF

Entity Framework and MySQL

Thu, 11 Sep 2008 04:09:31 GMT

MySQL are going to support Entity Framework, they are going to tell how to use EF with MySQL in their webinar.

Persistence Ignorance (POCO) Adapter for Entity Framework V1

Wed, 10 Sep 2008 15:03:07 GMT

One of the limitations of Entity Framework V1 released as part of .NET Framework 3.5 SP1 and Visual Studio 2008 SP1 is lack of support for POCO entity objects. POCO stands for Plain Old CLR Object and refers to an object that does not have any persistence concerns and is not aware of persistence framework. Modern development approaches such as DDD (Domain-Driven Design) and TDD (Test-Driven Development) prefer clear separation of concerns which implies persistence ignorance. [...] We have recently published a sample called EFPocoAdapter that includes code generator and a supporting library that implements POCO object tracking on top of Entity Framework V1

Entity Framework and some Architectural Decisions

Thu, 04 Sep 2008 05:39:20 GMT

A conversation between myself, Muhammad, and the community about how to tackle Entity Framework in a mult-layered application similar to how MVC Storefront application works, but effectively utilizing EF. We are hoping to have community feedback on possible approaches to tackle this.

LINQ to Entities, Workarounds on what is not supported

Mon, 01 Sep 2008 22:20:05 GMT

LINQ to Entities, Workarounds on what is not supported. 2 ways to get ride of what is not supported in LINQ to Entities.