Book Image

ASP.NET Core 6 and Angular - Fifth Edition

By : Valerio De Sanctis
Book Image

ASP.NET Core 6 and Angular - Fifth Edition

By: Valerio De Sanctis

Overview of this book

Every full-stack ninja needs the tools to operate on front-end and back-end application development. This web app development book takes a hands-on, project-based approach to provide you with all the tools and techniques that web developers need to create, debug, and deploy efficient web applications using ASP.NET Core and Angular. The fifth edition has been updated to cover advanced topics such as Minimal APIs, Web APIs with GraphQL, real-time updates with SignalR, and new features in .NET 6 and Angular 13. You begin by building 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 (.NET 6) and Jasmine, as well as Karma for Angular. After adding authentication and authorization to your apps, you will explore progressive web applications, learning about their technical requirements, testing processes, and how to convert a standard web application to a PWA. By the end of this web development 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 (18 chapters)
Other Books You May Enjoy

Health checks in Angular

It’s now time to build an Angular component that is capable of fetching and displaying the structured JSON data we managed to pull off in the previous sections.

As we know from Chapter 3, Looking Around, an Angular component is commonly made of four separate files, as follows:

  • The component (.ts) file, written in TypeScript and containing the component class, together with all the module references, functions, variables, and so on
  • The template (.html) file, written in HTML and extended with the Angular template syntax, which defines the UI layout architecture
  • The style (.css) file, written in CSS and containing the Cascading Style Sheets rules and definitions for drawing the UI
  • The test (.spec.ts) file, written in TypeScript and containing the tests that will be run by Karma

Although the aforementioned four-files approach is arguably the most practical one, the only required file is the component one...