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

Front-end debugging

In this section, we’ll briefly review the various front-end debugging options we have available (Visual Studio or the browser’s developer tools). Right after that, we’ll take a look at some Angular features that we can leverage to increase our awareness of the various tasks performed by our client-side application under the hood and debug them.

Visual Studio JavaScript debugging

Front-end debugging works just like back-end debugging, thanks to the JavaScript debugging feature of Visual Studio. The JavaScript debugger is not enabled by default, but the Visual Studio IDE will automatically ask whether to activate it or not the first time we put a breakpoint on a JavaScript (or TypeScript) file and run our app in debug mode.

As of the time of writing, client-side debugging support is only provided for Chrome and Microsoft Edge. On top of that, since we’re using TypeScript and not JavaScript directly, the use of source maps is...