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

Implementing DI with Autofac


In this recipe, we will use Autofac as a DI container to compose our application's object graph. It is famous, performant, and has a lot of features.

ASP.NET Core has an out-of-the-box DI container. In this chapter, we'll use another DI container-Autofac. Autofac is very well-received by the community.

An inbuilt DI container is very lightweight and doesn't support every feature that full-fledged DI containers support.

Autofac is also very light, but it has almost every feature that you would expect from a complete DI container library.

Getting ready

In the two previous recipes, we resolved the dependency on ServiceProduct by using the native IOC component in ASP.NET Core. This time, that will be done by a third-party component called Autofac. Now, in ASP.NET applications, we will be able to manage MVC, WebAPI, and SignalR components with the same IOC container.

How to do it...

As in the first recipe, we do the following:

  1. Inject the ServiceProducts class by using a constructor...