Book Image

ASP.NET Core MVC 2.0 Cookbook

By : Jason De Oliveira, Engin Polat, Stephane Belkheraz
Book Image

ASP.NET Core MVC 2.0 Cookbook

By: Jason De Oliveira, Engin Polat, Stephane Belkheraz

Overview of this book

The ASP.NET Core 2.0 Framework has been designed to meet all the needs of today’s web developers. It provides better control, support for test-driven development, and cleaner code. Moreover, it’s lightweight and allows you to run apps on Windows, OSX and Linux, making it the most popular web framework with modern day developers. This book takes a unique approach to web development, using real-world examples to guide you through problems with ASP.NET Core 2.0 web applications. It covers Visual Studio 2017- and ASP.NET Core 2.0-specifc changes and provides general MVC development recipes. It explores setting up .NET Core, Visual Studio 2017, Node.js modules, and NuGet. Next, it shows you how to work with Inversion of Control data pattern and caching. We explore everyday ASP.NET Core MVC 2.0 patterns and go beyond it into troubleshooting. Finally, we lead you through migrating, hosting, and deploying your code. By the end of the book, you’ll not only have explored every aspect of ASP.NET Core MVC 2.0, you’ll also have a reference you can keep coming back to whenever you need to get the job done.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Configuring the IOC life cycle for the repository pattern


In this recipe, we will learn a simple way of registering, resolving, and giving a life cycle to EF in ASP.NET Core.

Getting ready

We will inject EF in the ConfigureServices method of Statup.cs. The IServiceCollection interface parameter of ConfigureServices already has some helpers for the most common libraries used in ASP.NET MVC.

This code does not exist by default in the empty project in Visual Studio's ASP.NET Core templates, but it already exists if we use a Web Application ASP.NET Core template.

After that, we will add a class that inherits from DbContext to our application to perform database operations that throw an ORM. Finally, we will create a repository layer between the application and the database persistence layer (even if all the code is physically in the same application) before configuring its life cycle.

But, first of all, let's create a database on SQL Server (from 2008 to 2014) named CookBook.

After that, we will create...