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


Storing and retrieving data is an essential part of most web applications, and you can choose all kinds of databases to work with. EF Core is an O/RM that lets you write classes and LINQ queries, and those will be mapped to the database tables and to SQL statements without you needing to leave the comfort of the C# language. In this chapter, I explained how to work with EF Core and how you can use the DbContext base class to create a bridge between your classes, the database, and the conventional mapping it uses. You've seen how to store data and how to retrieve it with various LINQ operators. You also added automatic migrations to your application, which allows the database to be created and migrated to newer versions automatically without the need to run scripts in the database server itself.

I explained why you shouldn't use the same types of your data model when you return responses from your APIs, and instead, use DTOs. To make development easier, I introduced AutoMapper and...