Book Image

ASP.NET Core 2 and Angular 5

By : Valerio De Sanctis
Book Image

ASP.NET Core 2 and Angular 5

By: Valerio De Sanctis

Overview of this book

Become fluent in both frontend and backend web development by combining the impressive capabilities of ASP.NET Core 2 and Angular 5 from project setup right through the deployment phase. Full-stack web development means being able to work on both the frontend and backend portions of an application. The frontend is the part that users will see or interact with, while the backend is the underlying engine, that handles the logical flow: server configuration, data storage and retrieval, database interactions, user authentication, and more. Use the ASP.NET Core MVC framework to implement the backend with API calls and server-side routing. Learn how to put the frontend together using top-notch Angular 5 features such as two-way binding, Observables, and Dependency Injection, build the Data Model with Entity Framework Core, style the frontend with CSS/LESS for a responsive and mobile-friendly UI, handle user input with Forms and Validators, explore different authentication techniques, including the support for third-party OAuth2 providers such as Facebook, and deploy the application using Windows Server, SQL Server, and the IIS/Kestrel reverse proxy.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Summary


Before moving further, let's do a quick recap of what we did throughout this chapter.

We started working on the server-side aspects of our project. Having replaced the fake data provider with a real one, we made good use of it by implementing the Put, Post, and Delete action methods within our .NET Web API Controllers, mapping our Entities to their respective ViewModels--and the other way around--with the help of the Mapster package library. However, we shortly acknowledged the fact that we were writing a lot of duplicate code; in order to reduce this, we implemented a BaseApiController class that we used to do some common and repeating tasks, such as making the DbContext available through dependency injection and providing a handy JsonSettings property. We then derived all our web API controllers from that class and trimmed their source code accordingly.

Right after that, we switched to the client side and implemented the components required to run the new APIs within our Angular...