Book Image

Hands-On Full-Stack Web Development with ASP.NET Core

By : Tamir Dresher, Amir Zuker, Shay Friedman
Book Image

Hands-On Full-Stack Web Development with ASP.NET Core

By: Tamir Dresher, Amir Zuker, Shay Friedman

Overview of this book

Today, full-stack development is the name of the game. Developers who can build complete solutions, including both backend and frontend products, are in great demand in the industry, hence being able to do so a desirable skill. However, embarking on the path to becoming a modern full-stack developer can be overwhelmingly difficult, so the key purpose of this book is to simplify and ease the process. This comprehensive guide will take you through the journey of becoming a full-stack developer in the realm of the web and .NET. It begins by implementing data-oriented RESTful APIs, leveraging ASP.NET Core and Entity Framework. Afterward, it describes the web development field, including its history and future horizons. Then, you’ll build webbased Single-Page Applications (SPAs) by learning about numerous popular technologies, namely TypeScript, Angular, React, and Vue. After that, you’ll learn about additional related concerns involving deployment, hosting, and monitoring by leveraging the cloud; specifically, Azure. By the end of this book, you’ll be able to build, deploy, and monitor cloud-based, data-oriented, RESTful APIs, as well as modern web apps, using the most popular frameworks and technologies.
Table of Contents (22 chapters)
Title Page
PacktPub.com
Contributors
Preface
Index

Summary


In this chapter, we covered some of the tools and techniques that you can use to make it easier for you and the users of your API, who are developers themselves, to find and diagnose errors in your application.

Logging is one of the most helpful things you have in case of a problem. Often, it is the only way for you to find out what happened when the error occurred. The new logging framework that ASP.NET Core introduced is integrated very nicely with the ASP.NET Core request pipeline, and using it in your application code is straightforward. There are many logging providers that you can use, and I've shown you how you can use Application Insights, which provides a nice search window inside Visual Studio, along with other diagnostic utilities that can be used when running in production.

Because the users of your API are developers themselves, you need to make sure that they can consume the errors from your application and deal with them gracefully. I've shown you how to add a global...