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
About the Author
About the Reviewers
Customer Feedback

Creating Entities

We’ll definitely make use of one of the big advantages of the Code-First approach and start writing our Entity classes immediately, without worrying too much about what Database Engine we’ll use.


Truth be told, we already know something about what we’ll eventually use. We won’t be adopting a NoSQL solution, as they are not supported by EF yet; we also don’t want to commit ourselves into purchasing expensive license plans, so Oracle and the commercial editions of SQL Server are most likely out of the picture as well.

This leaves us with relatively few choices: SQL Server Compact Edition, SQL Server Express, MySql, or other less-known solutions such as PostgreSql. That being said, adopting Code-First will give us the chance to postpone the call until our Data Model is ready.


Let's start with the entity that will be used to store all the user-related info. We'll use it for a number of useful tasks, such as keeping record of who created each quiz, tracking those...