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

Introduction


In this chapter, we will learn what SOLID principles are, what the IOC, DI, and service locator patterns are, why we should use these patterns, what problems they solve, what tools we can use to solve them, and how they are implemented natively in ASP.NET Core.

Those who know all the concepts surrounding IOC and DI can go directly to the first recipe of this chapter. For the rest, we will show you some of these concepts in this introduction.

First of all, we have to follow these common design principles when programming with object-oriented languages:

  • Keep It Simple, Stupid: We have to keep our code simple and not over-complicate. Stupid does not mean silly.
  • Don't Repeat Yourself: Every piece of knowledge must have a single, unambiguous, authoritative representation within a system. In other words, we try to use abstraction in our system, avoiding repetition and not duplicating logic.
  • Tell, Don't Ask: We tell objects what to do instead of asking them what they should do. This practice...