Skip to main content
Entity Framework Databinding with WPF

Updated: October 23, 2016

This step-by-step walkthrough shows how to bind POCO types to WPF controls in a “master-detail" form. The application uses the Entity Framework APIs to populate objects with data from the database, track changes, and persist data to the database.

The model defines two types that participate in one-to-many relationship: Category (principal\master) and Product (dependent\detail). Then, the Visual Studio tools are used to bind the types defined in the model to the WPF controls. The WPF data-binding framework enables navigation between related objects: selecting rows in the master view causes the detail view to update with the corresponding child data.

The screen shots and code listings in this walkthrough are taken from Visual Studio 2013 but you can complete this walkthrough with Visual Studio 2012 or Visual Studio 2010.

With previous version of Entity Framework we used to recommend using the Database option when creating a new Data Source based on a model created with the EF Designer. This was because the designer would generate a context that derived from ObjectContext and entity classes that derived from EntityObject. Using the Database option would help you write the best code for interacting with this API surface.

The EF Designers for Visual Studio 2012 and Visual Studio 2013 generate a context that derives from DbContext together with simple POCO entity classes. With Visual Studio 2010 we recommend swapping to a code generation template that uses DbContext as described later in this walkthrough.

When using the DbContext API surface you should use the Object option when creating a new Data Source, as shown in this walkthrough.

If needed, you can revert to ObjectContext based code generation for models created with the EF Designer.

You need to have Visual Studio 2013, Visual Studio 2012 or Visual Studio 2010 installed to complete this walkthrough.

If you are using Visual Studio 2010, you also have to install NuGet. For more information, see Installing NuGet.

  • Open Visual Studio
  • File -> New -> Project….
  • Select Windows in the left pane and WPFApplication in the right pane
  • Enter WPFwithEFSample as the name
  • Select OK
  • In Solution Explorer, right-click on the WinFormswithEFSample project
  • Select Manage NuGet Packages…
  • In the Manage NuGet Packages dialog, Select the Online tab and choose the EntityFramework package
  • Click Install

    Note: In addition to the EntityFramework assembly a reference to System.ComponentModel.DataAnnotations is also added. If the project has a reference to System.Data.Entity, then it will be removed when the EntityFramework package is installed. The System.Data.Entity assembly is no longer used for Entity Framework 6 applications.

In this walkthrough you can chose to implement a model using Code First or the EF Designer. Complete one of the two following sections.

Option 1: Define a Model using Code First

This section shows how to create a model and its associated database using Code First. Skip to the next section (Option 2: Define a model using Database First) if you would rather use Database First to reverse engineer your model from a database using the EF designer

When using Code First development you usually begin by writing .NET Framework classes that define your conceptual (domain) model.

  • Add a new class to the WPFwithEFSample:
    • Right-click on the project name
    • Select Add, then New Item
    • Select Class and enter Product for the class name
  • Replace the Product class definition with the following code:
    namespace WPFwithEFSample
        public class Product
            public int ProductId { get; set; }
            public string Name { get; set; }

            public int CategoryId { get; set; }
            public virtual Category Category { get; set; }

-   Add a **Category** class with the following definition:

    using System.Collections.ObjectModel;

    namespace WPFwithEFSample
        public class Category
            public Category()
                this.Products = new ObservableCollection<Product>();
            public int CategoryId { get; set; }
            public string Name { get; set; }

            public virtual ObservableCollection<Product> Products { get; private set; }

The Products property on the Category class and Category property on the Product class are navigation properties. In Entity Framework, navigation properties provide a way to navigate a relationship between two entity types.

In addition to defining entities, you need to define a class that derives from DbContext and exposes DbSet<TEntity> properties. The DbSet<TEntity> properties let the context know which types you want to include in the model.

An instance of the DbContext derived type manages the entity objects during run time, which includes populating objects with data from a database, change tracking, and persisting data to the database.

  • Add a new ProductContext class to the project with the following definition:
    using System.Data.Entity;

    namespace WPFwithEFSample
        public class ProductContext : DbContext
            public DbSet<Category> Categories { get; set; }
            public DbSet<Product> Products { get; set; }

Compile the project.

Option 2: Define a model using Database First

This section shows how to use Database First to reverse engineer your model from a database using the EF designer. If you completed the previous section (Option 1: Define a model using Code First), then skip this section and go straight to the Lazy Loading section.

Create an Existing Database

Typically when you are targeting an existing database it will already be created, but for this walkthrough we need to create a database to access.

The database server that is installed with Visual Studio is different depending on the version of Visual Studio you have installed:

  • If you are using Visual Studio 2010 you'll be creating a SQL Express database.
  • If you are using Visual Studio 2012 then you'll be creating a LocalDb database.

Let's go ahead and generate the database.

  • View -> Server Explorer

  • Right click on Data Connections -> Add Connection…

  • If you haven’t connected to a database from Server Explorer before you’ll need to select Microsoft SQL Server as the data source


  • Connect to either LocalDb ((localdb)\v11.0) or SQL Express (.\SQLEXPRESS), depending on which one you have installed, and enter Products as the database name



  • Select OK and you will be asked if you want to create a new database, select Yes


  • The new database will now appear in Server Explorer, right-click on it and select New Query

  • Copy the following SQL into the new query, then right-click on the query and select Execute

    CREATE TABLE [dbo].[Categories] (
        [CategoryId] [int] NOT NULL IDENTITY,
        [Name] [nvarchar](max),
        CONSTRAINT [PK_dbo.Categories] PRIMARY KEY ([CategoryId])

    CREATE TABLE [dbo].[Products] (
        [ProductId] [int] NOT NULL IDENTITY,
        [Name] [nvarchar](max),
        [CategoryId] [int] NOT NULL,
        CONSTRAINT [PK_dbo.Products] PRIMARY KEY ([ProductId])

    CREATE INDEX [IX_CategoryId] ON [dbo].[Products]([CategoryId])

    ALTER TABLE [dbo].[Products] ADD CONSTRAINT [FK_dbo.Products_dbo.Categories_CategoryId] FOREIGN KEY ([CategoryId]) REFERENCES [dbo].[Categories] ([CategoryId]) ON DELETE CASCADE

Reverse Engineer Model

We’re going to make use of Entity Framework Designer, which is included as part of Visual Studio, to create our model.

  • Project -> Add New Item…

  • Select Data from the left menu and then ADO.NET Entity Data Model

  • Enter ProductModel as the name and click OK

  • This launches the Entity Data Model Wizard

  • Select Generate from Database and click Next


  • Select the connection to the database you created in the first section, enter ProductContext as the name of the connection string and click Next


  • Click the checkbox next to ‘Tables’ to import all tables and click ‘Finish’


Once the reverse engineer process completes the new model is added to your project and opened up for you to view in the Entity Framework Designer. An App.config file has also been added to your project with the connection details for the database.

Additional Steps in Visual Studio 2010

If you are working in Visual Studio 2010 then you will need to update the EF designer to use EF6 code generation.

  • Right-click on an empty spot of your model in the EF Designer and select Add Code Generation Item…
  • Select Online Templates from the left menu and search for DbContext
  • Select the EF 6.x DbContext Generator for C#, enter ProductsModel as the name and click Add

Updating code generation for data binding

EF generates code from your model using T4 templates. The templates shipped with Visual Studio or downloaded from the Visual Studio gallery are intended for general purpose use. This means that the entities generated from these templates have simple ICollection<T> properties. However, when doing data binding using WPF it is desirable to use ObservableCollection for collection properties so that WPF can keep track of changes made to the collections. To this end we will to modify the templates to use ObservableCollection.

  • Open the Solution Explorer and find ProductModel.edmx file

  • Find the file which will be nested under the ProductModel.edmx file


  • Double-click on the file to open it in the Visual Studio editor

  • Find and replace the two occurrences of “ICollection” with “ObservableCollection”. These are located approximately at lines 296 and 484.

  • Find and replace the first occurrence of “HashSet” with “ObservableCollection”. This occurrence is located approximately at line 50. Do not replace the second occurrence of HashSet found later in the code.

  • Find and replace the only occurrence of “System.Collections.Generic” with “System.Collections.ObjectModel”. This is located approximately at line 424.

  • Save the file. This should cause the code for entities to be regenerated. If the code does not regenerate automatically, then right click on and choose “Run Custom Tool”.

If you now open the Category.cs file (which is nested under then you should see that the Products collection has the type ObservableCollection<Product>.

Compile the project.

The Products property on the Category class and Category property on the Product class are navigation properties. In Entity Framework, navigation properties provide a way to navigate a relationship between two entity types.

EF gives you an option of loading related entities from the database automatically the first time you access the navigation property. With this type of loading (called lazy loading), be aware that the first time you access each navigation property a separate query will be executed against the database if the contents are not already in the context.

When using POCO entity types, EF achieves lazy loading by creating instances of derived proxy types during runtime and then overriding virtual properties in your classes to add the loading hook. To get lazy loading of related objects, you must declare navigation property getters as public and virtual (Overridable in Visual Basic), and you class must not be sealed (NotOverridable in Visual Basic). When using Database First navigation properties are automatically made virtual to enable lazy loading. In the Code First section we chose to make the navigation properties virtual for the same reason

Add the classes that are defined in the model as data sources for this WPF application.

  • Double-click MainWindow.xaml in Solution Explorer to open the main form

  • From the main menu, select Project -> Add New Data Source … (in Visual Studio 2010, you need to select Data -> Add New Data Source…)

  • In the Choose a Data Source Typewindow, select Object and click Next

  • In the Select the Data Objects dialog, unfold the WPFwithEFSample two times and select Category
    There is no need to select the Product data source, because we will get to it through the Product’s property on the Category data source


  • Click Finish.

  • The Data Sources window is opened next to the MainWindow.xaml window If the Data Sources window is not showing up, select View -> Other Windows-> Data Sources

  • Press the pin icon, so the Data Sources window does not auto hide. You may need to hit the refresh button if the window was already visible.


  • Select the **Category **data source and drag it on the form.

The following happened when we dragged this source:

  • The categoryViewSource resource and the** categoryDataGrid** control were added to XAML. For more information about DataViewSources, see
  • The DataContext property on the parent Grid element was set to "{StaticResource categoryViewSource }". The categoryViewSource resource serves as a binding source for the outer\parent Grid element. The inner Grid elements then inherit the DataContext value from the parent Grid (the categoryDataGrid’s ItemsSource property is set to "{Binding}").
        <CollectionViewSource x:Key="categoryViewSource" 
                                d:DesignSource="{d:DesignInstance {x:Type local:Category}, CreateList=True}"/>
    <Grid DataContext="{StaticResource categoryViewSource}">
        <DataGrid x:Name="categoryDataGrid" AutoGenerateColumns="False" EnableRowVirtualization="True" 
                    ItemsSource="{Binding}" Margin="13,13,43,191" 
                <DataGridTextColumn x:Name="categoryIdColumn" Binding="{Binding CategoryId}" 
                                    Header="Category Id" Width="SizeToHeader"/>
                <DataGridTextColumn x:Name="nameColumn" Binding="{Binding Name}" 
                                    Header="Name" Width="SizeToHeader"/>

Now that we have a grid to display Categories let's add a details grid to display the associated Products.

  • Select the **Products **property from under the **Category **data source and drag it on the form.
    • The categoryProductsViewSource resource and productDataGrid grid are added to XAML
    • The binding path for this resource is set to Products
    • WPF data-binding framework ensures that only Products related to the selected Category show up in productDataGrid
  • From the Toolbox, drag Button on to the form. Set the Name property to buttonSave and the Content property to Save.

The form should look similar to this:


It's time to add some event handlers to the main window.

  • In the XAML window, click on the <Window element, this selects the main window

  • In the Properties window choose Events at the top right, then double-click the text box to right of the Loaded label


  • Also add the Click event for the Save button by double-clicking the Save button in the designer.

This brings you to the code behind for the form, we'll now edit the code to use the ProductContext to perform data access. Update the code for the MainWindow as shown below.

The code declares a long-running instance of ProductContext. The ProductContext object is used to query and save data to the database. The Dispose() on the ProductContext instance is then called from the overridden OnClosing method. The code comments provide details about what the code does.

    using System.Data.Entity;
    using System.Linq;
    using System.Windows;

    namespace WPFwithEFSample
        public partial class MainWindow : Window
            private ProductContext _context = new ProductContext();
            public MainWindow()

            private void Window_Loaded(object sender, RoutedEventArgs e)
                System.Windows.Data.CollectionViewSource categoryViewSource =

                // Load is an extension method on IQueryable, 
                // defined in the System.Data.Entity namespace.
                // This method enumerates the results of the query, 
                // similar to ToList but without creating a list.
                // When used with Linq to Entities this method 
                // creates entity objects and adds them to the context.

                // After the data is loaded call the DbSet<T>.Local property 
                // to use the DbSet<T> as a binding source.
                categoryViewSource.Source = _context.Categories.Local;

            private void buttonSave_Click(object sender, RoutedEventArgs e)
                // When you delete an object from the related entities collection 
                // (in this case Products), the Entity Framework doesn’t mark 
                // these child entities as deleted.
                // Instead, it removes the relationship between the parent and the child
                // by setting the parent reference to null.
                // So we manually have to delete the products 
                // that have a Category reference set to null.

                // The following code uses LINQ to Objects 
                // against the Local collection of Products.
                // The ToList call is required because otherwise the collection will be modified
                // by the Remove call while it is being enumerated.
                // In most other situations you can use LINQ to Objects directly 
                // against the Local property without using ToList first.
                foreach (var product in _context.Products.Local.ToList())
                    if (product.Category == null)

                // Refresh the grids so the database generated values show up.

            protected override void OnClosing(System.ComponentModel.CancelEventArgs e)

  • Compile and run the application. If you used Code First, then you will see that a WPFwithEFSample.ProductContext database is created for you. If SQL Express is installed (included in Visual Studio 2010) then the database is created on your local SQL Express instance (.\SQLEXPRESS). If SQL Express is not installed then Code First will try and use LocalDb ((localdb)\v11.0) - LocalDb is included with Visual Studio 2012. Note: SQL Express will always get precedence if it is installed, even if you are using Visual Studio 2012

  • Enter a category name in the top grid and product names in the bottom grid Do not enter anything in ID columns, because the primary key is generated by the database


  • Press the Save button to save the data to the database

After the call to DbContext’s SaveChanges(), the IDs are populated with the database generated values. Because we called Refresh() after SaveChanges() the DataGrid controls are updated with the new values as well.