Book Image

ASP.NET Core 5 for Beginners

By : Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price
Book Image

ASP.NET Core 5 for Beginners

By: Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price

Overview of this book

ASP.NET Core 5 for Beginners is a comprehensive introduction for those who are new to the framework. This condensed guide takes a practical and engaging approach to cover everything that you need to know to start using ASP.NET Core for building cloud-ready, modern web applications. The book starts with a brief introduction to the ASP.NET Core framework and highlights the new features in its latest release, ASP.NET Core 5. It then covers the improvements in cross-platform support, the view engines that will help you to understand web development, and the new frontend technologies available with Blazor for building interactive web UIs. As you advance, you’ll learn the fundamentals of the different frameworks and capabilities that ship with ASP.NET Core. You'll also get to grips with securing web apps with identity implementation, unit testing, and the latest in containers and cloud-native to deploy them to AWS and Microsoft Azure. Throughout the book, you’ll find clear and concise code samples that illustrate each concept along with the strategies and techniques that will help to develop scalable and robust web apps. By the end of this book, you’ll have learned how to leverage ASP.NET Core 5 to build and deploy dynamic websites and services in a variety of real-world scenarios.
Table of Contents (19 chapters)
Section 1 – Crawling
Section 2 – Walking
Section 3 – Running

Running Redis on Docker

In this section, we will run the popular open source in-memory cache Redis. Redis is a data structure store, meaning it stores things such as strings, lists, sets, sorted sets, and hashes and supports queries against stored data. Redis has been developed for over a decade, has a large community, and is worth checking out if you have not done so already.

Running Redis as a container for local development makes a lot of sense. By using a container, we don't have to install Redis onto the machine or worry about security permissions. With a container, the setup and security are already done. The limitation, though, is that we only have access to some Redis options. If there is an option that is not supported by the base Redis image, then I recommend you to create custom Redis images using the Redis image as a base.

Starting Redis

Start a Redis container using the run command:

docker run --name myRedis -p 6379:6379 -d redis

With this command...