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 a view component/controller class


In this recipe, we will learn how to use/create a hybrid ViewComponent/controller class.

Getting ready

We will create an empty web application with ASP.NET Core MVC enabled, adding the MVC dependency to the project:

"Microsoft.AspNetCore.Mvc": "2.0.0" 

In this recipe, we will create a basket component and place it in the _Layout.cstml file. This way, the basket component will be visible for every page. The basket object will be stored in Session.

How to do it...

  1. Let's create all the code we need to display some products to add to the basket. The models will have to be serializable (models, services):
[Serializable] 
public class Product 
{ 
  public int Id { get; set; } 
  public string Name { get; set; } 
  public decimal Price { get; set; } 
} 
 
[Serializable] 
public class Basket 
{ 
  public List<Product> ListProducts { get; set; } 
  public decimal Total { get; set; } 
 
  public Basket() 
  { 
    ListProducts = new List<Product>();...