Book Image

ASP.NET Core 5 and Angular - Fourth Edition

By : Valerio De Sanctis
Book Image

ASP.NET Core 5 and Angular - Fourth Edition

By: Valerio De Sanctis

Overview of this book

Learning full-stack development calls for knowledge of both front-end and back-end web development. ASP.NET Core 5 and Angular, Fourth Edition will enhance your ability to create, debug, and deploy efficient web applications using ASP.NET Core and Angular. This revised edition includes coverage of the Angular routing module, expanded discussion on the Angular CLI, and detailed instructions for deploying apps on Azure, as well as both Windows and Linux. Taking care to explain and challenge design choices made throughout the text, Valerio teaches you how to build a data model with Entity Framework Core, alongside utilizing the Entity Core Fluent API and EntityTypeConfiguration class. You’ll learn how to fetch and display data and handle user input with Angular reactive forms and front-end and back-end validators for maximum effect. Later, you will perform advanced debugging and explore the unit testing features provided by xUnit.net (.NET 5) and Jasmine, as well as Karma for Angular. After adding authentication and authorization to your apps, you will explore progressive web applications (PWAs), learning about their technical requirements, testing, and converting SWAs to PWAs. By the end of this book, you will understand how to tie together the front end and back end to build and deploy secure and robust web applications.
Table of Contents (15 chapters)
13
Other Books You May Enjoy
14
Index

Front-End and Back-End Interactions

Now that we have a minimalistic—yet fully working—ASP.NET Core and Angular web app up and running, we can definitely start to build some stuff. In this chapter, we're going to learn the basics of client-side and server-side interactions: in other words, how the front-end (Angular) can fetch some relevant data from the back-end (ASP.NET Core) and display it on-screen, in a readable fashion.

Wait a minute... as a matter of fact, we should've already got the gist of how it works, right? We saw this in Chapter 2, Looking Around, before getting rid of Angular's FetchDataComponent and ASP.NET Core's WeatherForecastController.cs classes and files. The Angular component (front-end) pulls data from the ASP.NET controller (back-end) and then puts it on the browser screen (UI) for display.

Such a statement is absolutely correct. However, controllers aren't the only way for our ASP.NET Core back-end to serve data...