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


We started this chapter by enumerating a number of things we couldn’t implement due to our Dummy Data Provider limitations; in order to overcome these, we chose to replace it with a real Data Provider built upon a persistent Database.

Entity Framework Core seemed an obvious choice to get what we want, so we added its relevant packages to our project; we briefly enumerated the available Data Modeling approaches and resorted to using Code-First due to its flexibility.

Right after that, we proceeded to create our entity classes--ApplicationUser, Quiz, Question, Answer and Result--along with a set of relationships taking advantage of the renowned Entity Framework Core’s Convention over Configuration approach. Then, we built our ApplicationDbContext class accordingly.

After completing our Data Model, we chose the Database Engine, quickly resorting to the Visual Studio's default MSSQL LocalDb instance; we added the connection string to the appsettings.json file and passed it to ApplicationDbContext...