Entity Framework (EF) has evolved quite a bit and as it has evolved it has become more and more confusing to keep up with its changes which have been introduced a series of addons in the form of libraries. You can sit down and read pages of documentation to understand what has happened, but when you just need to dive into something because of time constraints it is frustrating. That has led me to ask the question “How do I install and use EF 4.3.1?” Well unfortunately it is not a one click install, it is a multi-step installation.


  • You are using Visual Studio 2010
  • You are using the .Net 4.0 Framework
  • You need to either create a new EDMX or you have an existing EDMX using the stock version of EF that comes with .Net 4.0 and VS2010 which is EF 4.0
  • You are using the database first method (versus code first method)
  • You have NuGet installed (this is required)
  • You have made a backup of your project before continuing (just in case things go sideways)

Can I used EF 5.0 instead?

If you are using Visual Studio 2010 (VS2010), then the answer is NO. EF 5.0 is supported in Visual Studio 2012 (VS2012) for .Net 4.5, if you have access to VS2012 then I say go for it. I haven’t had a chance to move on yet myself.

Part A: Setting up a Project with an EDMX file

  1. If you don’t already have an EDMX file, then either create a new project or use an existing one, and add a new item to your project (Right click on project file > Add > New Item…)
  2. Under “Installed Templates” (left hand side) select “Data” and then select ADO.Net Entity Data Model – name it however you see fit. Example: InventoryModel.edmx
  3. Follow the wizard and setup your edmx as you would normally – add which ever tables you need etc…
  4. After you have finished adding your edmx, it is time to install EF 4.3.1
Step 1


Step 2-4

Part B: Installing EF 4.3.1
Reminder: You must have NuGet installed to perform these steps

  1. Open up the NuGet Package Manager Console: Tools > Library Package Manager > Package Manager Console
  2. Make sure you have the correct project selected and at the command prompt enter the following command sans soft quotes: “Install-Package EntityFramework -Version 4.3.1” Where did you find this command? After pressing the enter key a bunch of stuff happens. Some of that stuff is a dll named “EntityFramework” is added a dll reference to your project. If you haven’t used NuGet before then don’t be alarmed by the config file named “packages.config”, that is added when adding packages using NuGet.


Step 1


Step 2


Verification 1


Verification 2

Part C: Using EF 4.3.1 and a DBConext Generator of your Choosing
Say hello to the System.Data.Entity.DBContext Pattern, this is essentially what you have enabled yourself to use by installing EF 4.3.1, there are a number of new properties and awesome methods that have been added to the DBContext pattern. You are switching over from the System.Data.Objects.ObjectContext pattern which comes stock with EF 4.0 in VS2010.

Context Generators

You should use the right context generator for the job and each context generator has its own quirks. Really the defining line in my opinion on which context generator to use is by asking yourself, “Do I need to have an SOA or am I going to use WCF?” If the answer is yes, then you want to use a context generator with WCF support. If the answer is no, or you don’t mind writing your own translation layer (converting your entities to POCO manually) then you can just use the regular DbContext Generator.

For argument’s sake, we are going to use the DbContext Generator since it is basically the next step up from the original ObjectContext generator. It will not generate serializable objects, so don’t bother with it for WCF.

  1. Add a new Code Generation Item by opening your EDMX file > right click on blank space > select “Add Code Generation Item…”
  2. Click on Online Templates located on the lower left hand side of the left pane.
  3. Click on “EF 4.x DbContext Generator for C#”
  4. Name it something different from your EDMX, like “”
  5. Press the Add button – automatically this model will generate one file per entity and your old ObjectContext will no longer be valid. You will now have to use the new DbContext for any existing code (if you had any).


Step 1


Step 2-5

What Now?

You are probably thinking, “Okay great, I upgraded from 4.0 to 4.3.1, but what can I do that I couldn’t do before?”, well right off the bat there are two very useful things that I can name. There is now a Database Property, that will easily allow you to get your connection string, not too exciting, but not bad either. The second and most valuable thing in my opinion is the ability to selectively update fields/properties/columns when making an update to an entity.

I Upgraded and Everything is Broken Now!

If you were upgrading an existing project from EF 4.0 to 4.3.1, then yes, there is a good chance a lot of your code will be broken because the 4.0 syntax is different from the 4.3.1 syntax, but the idea remains the same it is still an ORM. For example in 4.0 using the ObjectContext to do an insert into a collection of Books you would write: context.Books.AddObject(book); but in 4.3.1 using the DBContext you will write context.Books.Add(book); – not a major difference, just syntactically different.

Useful Code Snippets

Here are some useful code snippets, specifically extension methods, for stuff you are probably going to do one way or another.


Usage Examples

DbContext Generator with WCF Support

If you require WCF support, then I strongly suggest using the DBContext Generator with WCF Support as opposed to the POCO generator. The classes that are generated are lightweight, so much so that you lose a little bit of functionality unfortunately. With the regular DbContext Generator when you load an entity, any relational properties (collections of other entities related by Foreign Key), those relational properties are loaded for you. With the DbContext Generator with WCF Support, those relational properties are not loaded for you, you have to explicitly state that you want them loaded in your lambda expressions or linq queries.

How to Explicitly Load a Relational Property

For demonstration purposes, let’s say we have a Author and Book entities. Authors write multiple Books and therefore the Author Entity has a List<Book> property named Books. (Author.Books) – this is done in the database by taking the Author’s Primary Key (PK) AuthorID and placing it as a Foreign Key (FK) in the Book table, also named AuthorID. An explicit FK relationship is created in the DB. This is construed as a Relational Property automatically by EF when generating the entities for the model. If you do not explicitly load the this property it will be empty. Therefore to achieve this do the following:


Leave a Reply

Your email address will not be published. Required fields are marked *