Book Image

Modern Web Development with ASP.NET Core 3 - Second Edition

By : Ricardo Peres
Book Image

Modern Web Development with ASP.NET Core 3 - Second Edition

By: Ricardo Peres

Overview of this book

ASP.NET has been the preferred choice of web developers for a long time. With ASP.NET Core 3, Microsoft has made internal changes to the framework along with introducing new additions that will change the way you approach web development. This second edition has been thoroughly updated to help you make the most of the latest features in the framework, right from gRPC and conventions to Blazor, which has a new chapter dedicated to it. You’ll begin with an overview of the essential topics, exploring the Model-View-Controller (MVC) pattern, various platforms, dependencies, and frameworks. Next, you’ll learn how to set up and configure the MVC environment, before delving into advanced routing options. As you advance, you’ll get to grips with controllers and actions to process requests, and later understand how to create HTML inputs for models. Moving on, you'll discover the essential aspects of syntax and processes when working with Razor. You'll also get up to speed with client-side development and explore the testing, logging, scalability, and security aspects of ASP.NET Core. Finally, you'll learn how to deploy ASP.NET Core to several environments, such as Azure, Amazon Web Services (AWS), and Docker. By the end of the book, you’ll be well versed in development in ASP.NET Core and will have a deep understanding of how to interact with the framework and work cross-platform.
Table of Contents (26 chapters)
Section 1: The Fundamentals of ASP.NET Core 3
Section 2: Improving Productivity
Section 3: Advanced Topics
Appendix A: The dotnet Tool


View layouts are a must-have; try to avoid nested (or too nested) view layouts, as it may be difficult to understand the final result. Partial views are also very handy, but make sure you use them to avoid repeating code.

We should also avoid having code in views—for example, by specifying custom view classes; use filters for that purpose. We saw that we should consider the localization needs of your app upfront; it's very difficult and error-prone to refactor an existing app that does not use localization to introduce it.

Then, next, we saw that for security, you can use code or tag helpers to keep sensitive parts of your views secure.

Stick to the conventions in terms of folder names and the like. This will make things easier for everyone, currently and in the future, in your team.

We learned that _ViewImports.cshtml and _ViewStart.cshtml are your friends—use them for common code that you want to be applied to all your...