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

The model


The M in MVC means model, but what does a model really mean? The simplest definition is that model refers to the application problem-domain entities and their behavior, where behavior can be implemented in the entities themselves, or in a dedicated service class.

Classes that contain only properties with no logic are called Plain Old CLR Objects (POCO) classes. These are the type of classes that work best when received as input or returned as output from your APIs. It will save you many headaches if you stick to POCO classes in the external surface of your APIs. This will also keep you from making mistakes, namely exposing sensitive information such as your database structure, as your APIs grow. On the internals of your APIs, you can use any type of classes that you like, and in Chapter 5, Persisting Data with Entity Framework, you will learn how to use the Entity Framework (EF) core to work with classes that map to database tables and allow you to store data and query it.

Model...