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

Creating and working with areas


In this recipe, you will learn how to manage areas in ASP.NET Core. To do this, we will:

  • Create areas
  • Create area routes
  • Avoid area route conflict
  • Change the default views location
  • Create links for an area's action controllers

Getting ready

We created an empty web application with VS 2017.

How to do it...

When structuring an MVC application, sometimes, we need functional separation. The application we develop could be larger than it seems, such that we have several applications in an application. Areas give us the capability to create a lot of MVC structures in function of our needs, and give us a way to manage complex applications more easily. For example, in an e-commerce application, we could need different areas for the administration part of the website, which correspond to different roles (user managing, marketing, motor search reference, orders tracking, stock management), plus the website itself, of course.

Each area has its own controller, model, and view folders...