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 xUnit.net (.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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Free Chapter

Introducing ASP.NET and Angular

Introducing ASP.NET and Angular

Technical requirements

Two players, one goal

The ASP.NET Core revolution

What’s new in Angular?

Reasons for choosing .NET and Angular

Suggested topics

Getting Ready

Technical requirements

A full-stack approach

MPAs, SPAs, PWAs, and NWAs

An example SPA project

Preparing the workspace

Suggested topics

Looking Around

Technical requirements

Solution overview

The ASP.NET back-end

The Angular front-end

Getting to work

Suggested topics

Front-End and Back-End Interactions

Front-End and Back-End Interactions

Technical requirements

Introducing ASP.NET Core health checks

Health checks in Angular

Restyling the UI

Suggested topics

Data Model with Entity Framework Core

Data Model with Entity Framework Core

Technical requirements

The WorldCities web app

The data source

Creating the entities

Getting a SQL Server instance

Creating the database using Code-First

Populating the database

Entity controllers

Suggested topics

Fetching and Displaying Data

Fetching and Displaying Data

Technical requirements

Serving data with Angular Material

Adding countries to the loop

Suggested topics

Forms and Data Validation

Forms and Data Validation

Technical requirements

Exploring Angular forms

Building our first Reactive Form

Adding a new city

Understanding data validation

Introducing the FormBuilder

Improving the filter behavior

Suggested topics

Code Tweaks and Data Services

Code Tweaks and Data Services

Technical requirements

Optimizations and tweaks

Bug fixes and improvements

Suggested topics

Back-End and Front-End Debugging

Back-End and Front-End Debugging

Technical requirements

Back-end debugging

Front-end debugging

Application logging

Suggested topics

ASP.NET Core and Angular Unit Testing

ASP.NET Core and Angular Unit Testing

Technical requirements

ASP.NET Core unit tests

Angular unit tests

Suggested topics

Authentication and Authorization

Authentication and Authorization

Technical requirements

To auth, or not to auth

Proprietary auth with .NET Core

Updating the database

Implementing authentication in Angular

Finishing touches

Suggested topics

Progressive Web Apps

Progressive Web Apps

Technical requirements

PWA distinctive features

Implementing the PWA requirements

Handling the offline status

Testing the PWA capabilities

Suggested topics

Beyond REST – Web API with GraphQL

Beyond REST – Web API with GraphQL

Technical requirements

GraphQL versus REST

Implementing GraphQL

Suggested topics

Real-Time Updates with SignalR

Real-Time Updates with SignalR

Technical requirements

Real-time HTTP and Server Push

Implementing SignalR

Client-initiated Events

Suggested topics

Windows, Linux, and Azure Deployment

Windows, Linux, and Azure Deployment

Technical requirements

Getting ready for production

Windows deployment

Linux deployment

Azure App Service deployment

Suggested topics

Other Books You May Enjoy

Other Books You May Enjoy

Index

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Solution overview

The first thing that catches the eye is that, as we’ve already mentioned, the layout of a standard ASP.NET Core solution is quite different from what it used to be in ASP.NET 5 and earlier versions. The most notable thing is that we have two different projects – one for Angular (HealthCheck) and one for the ASP.NET Core Web API (HealthCheckAPI) – that start together and need to interact with each other. If we have previous “classic” ASP.NET single-project experience, we could find such an approach quite different from what we were used to working with.

The best thing about the new approach is that we’re instantly able to distinguish the ASP.NET back-end part from the Angular front-end part, which could be troublesome with the previous, single-project experience, when the two stacks were often intertwined.

Let’s quickly review their overall structure to better understand how each one of them works.