In this post I will be looking into EF 6.0 using the Code First Workflow and its support for stored procedures and more particularly how to display data using a stored procedure. I have posted something similar in this post https://weblogs.asp.net/dotnetstories/using-stored-procedures-in-an-asp-net-mvc-5-0-application-using-entity-framework-6-0 but this post described in detail how to insert, update and delete data in an ASP.Net MVC 6.0 application using stored procedures but not how to display data using a stored procedure. 

In this post I am going to discuss Dependency Injection pattern, explain why we need it and how to use it in our modern web applications based on the ASP.Net MVC paradigm.

In this post I am going to make the case why returning IQueryable from a Repository Pattern is an anti-pattern and why you should not do it.

In this post I will try to explain why the Repository Pattern is not redundant when we use an ORM like Entity Framework in our application.

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 create a hands on example, a sample ASP.Net MVC application where I will demonstrate the concept of ViewModels.

In this post I will use a simple ASP.Net 5.0 MVC application to implement a jQuery Ajax call to an ASP.Net MVC controller.

When developing/architecting our custom ASP.Net MVC applications we do use the Repository Pattern/Generic Repository Pattern.