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

Chapter 4. Data Model with Entity Framework Core

Our Single-Page Application is growing fine, yet it’s also starting to show its limits:

  • There’s no way we can add, update, or delete our sample records
  • We cannot properly implement our Login view, since it will require handling some sort of user authentication in terms of credential storage and session persistence, to say the least
  • Truth be told, we can’t even say we’re actually showing something close to our original plan; our quizzes are still shallow items with titles and descriptions put together by a sample method providing some autogenerated data

It’s time to get rid of that provisional demo and start working on the real thing. We won’t use Angular for the time being, as what we need to implement has little or nothing to do with the client-side portion of our app. Nonetheless, we’re fully aware of the fact that most entities of the Data Model we’re about to build will have their correspondence in an Angular model class, just like we did...