Book Image

.NET Core 2.0 By Example

By : Neha Shrivastava, Rishabh Verma
Book Image

.NET Core 2.0 By Example

By: Neha Shrivastava, Rishabh Verma

Overview of this book

With the rise in the number of tools and technologies available today, developers and architects are always exploring ways to create better and smarter solutions. Before, the differences between target platforms was a major roadblock, but that's not the case now. .NET Core 2.0 By Example will take you on an exciting journey to building better software. This book provides fresh and relevant content to .NET Core 2.0 in a succinct format that’s enjoyable to read. It also delivers concepts, along with the implications, design decisions, and potential pitfalls you might face when targeting Linux and Windows systems, in a logical and simple way. With the .NET framework at its center, the book comprises of five varied projects: a multiplayer Tic-tac-toe game; a real-time chat application, Let'sChat; a chatbot; a microservice-based buying-selling application; and a movie booking application. You will start each chapter with a high-level overview of the content, followed by the above example applications described in detail. By the end of each chapter, you will not only be proficient with the concepts, but you’ll also have created a tangible component in the application. By the end of the book, you will have built five solid projects using all the tools and support provided by the .NET Core 2.0 framework.
Table of Contents (16 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

ASP.NET Core 2.0 fundamentals


This section is a continuation of our journey of learning ASP.NET Core 2.0 fundamentals that we started in the previous chapter. We will (re)visit the fundamentals, so that we can use them correctly while coding the app. In this section, we will take a quick lap around MVC and we will further discuss routing, filters, error handling, and so on. Let's start with MVC.

Quick lap around MVC

MVC stands for Model-View-Controller. The intent of this pattern is to achieve separation of concerns. In general terms, we can draw an analogy of MVC with "Division of labour". In this architectural pattern, the application is divided into three distinct components: the Model, the View, and the Controller. When a user requests a resource in the server, it is routed to a Controller which works with the Model to perform user actions and/or CRUD (Create, Read, Update, Delete) operations. The Controller then chooses the View to display the user interface to the user, and provides...