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 the different mechanisms we can use to store data in our application development. We will learn about the server-side features in .NET, but not with IIS, because now with ASP.NET Core, we try to be server-agnostic and design the application with middlewares. This is why we will not cover IIS cache mechanisms we already know, such as output caching.

We will also learn about some HTML5 features to cache files or data on the client. This data can be either simple or complex data in JavaScript. If it is complex, we will store it as JSON.

To store this data, we will use JavaScript global variables named localStorage and sessionStorage. To cache files, we will prefer to use a manifest file.

Finally, we will learn how to store data as NoSQL data (or non-relational data as key-value pairs) in some client-side mechanism with IndexedDB, or using a distributed cache mechanism with Redis on Azure.

For the client-side cache features we will be talking about in...