DotNetStories
In this post I will try to define the Repository Pattern, explain what it is and how we must use it in my own words and according to my experience as a software engineer.
In this post I am going to provide you with a hands-on example on how to avoid writing your LINQ to Entities queries in a way that will hinder performance of your application. The aim of this post (hopefully a series of posts on performance and Entity Framework) is to highlight bad coding practices when architecting an applications that uses EF as the ORM to fetch and manipulate data from the data store. I am going to point out some practises and patterns that very often developers use and cause EF to create poor-performing T-SQL statements.
In this post I will demonstrate with a hands on demo how
to localise your ASP.Net MVC applications.
In this post I will demonstrate with a hands-on demo the importance of using patterns in an ASP.Net MVC application. I will use the Repository Pattern to create an additional abstract layer between my domain classes and the data layer.
In this post I will demonstrate with a hands-on example
how to use the Fluent API to map POCO classes
(set configurations) to SQL Server tables without using
the set of conventions Entity
Framework Code First expects.
In this blog post I will demonstrate with a hands-on
example how to use EF Code First Workflow to
create an entity data model, an .edmx file so I
can visualise my POCO classes
In this blog post I will try to explain with a hand-on demo how we can use Entity Framework Code first with an existing database. I will create the database and then I will use an ASP.Net MVC 4.0 application to demonstrate how to map Code First EF Workflow to the database.