Book Image

Learning ASP.NET Core 2.0

By : Jason De Oliveira, Michel Bruchet
Book Image

Learning ASP.NET Core 2.0

By: Jason De Oliveira, Michel Bruchet

Overview of this book

The ability to develop web applications that are highly efficient but also easy to maintain has become imperative to many businesses. ASP.NET Core 2.0 is an open source framework from Microsoft, which makes it easy to build cross-platform web applications that are modern and dynamic. This book will take you through all of the essential concepts in ASP.NET Core 2.0, so you can learn how to build powerful web applications. The book starts with a brief introduction to the ASP.NET Core framework and the improvements made in the latest release, ASP.NET Core 2.0. You will then build, test, and debug your first web application very quickly. Once you understand the basic structure of ASP.NET Core 2.0 web applications, you'll dive deeper into more complex concepts and scenarios. Moving on, we'll explain how to take advantage of widely used frameworks such as Model View Controller and Entity Framework Core 2 and you'll learn how to secure your applications. Finally, we'll show you how to deploy and monitor your applications using Azure, AWS, and Docker. After reading the book, you'll be able to develop efficient and robust web applications in ASP.NET Core 2.0 that have high levels of customer satisfaction and adoption.
Table of Contents (19 chapters)
Title Page
Credits
Foreword
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Understanding the Model View Controller pattern


The MVC pattern separates applications into three main layers—models, views, and controllers. One of the benefits of this pattern is the separation of concerns, also called the Single Responsibility Principle (SRP), which makes it possible to develop, debug, and test application features independently.

When using the MVC pattern, a user request is routed to a Controller, which will use a Model for retrieving data and performing actions. The Controller selects a corresponding view for display to the user, while providing it with the necessary data from the Model.

There is less impact if a layer (for example, Views) changes, since it is now loosely coupled to the other layers of your applications (for example, controllers and models).

It is also much easier to test the different layers of your applications. In the end, you will have better maintainability and more robust code by using this pattern:

Models

A Model contains the logical data structures...