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

Dealing with single entries

Our updated QuizController class gives us a way to retrieve a single Quiz entry; it will definitely be very useful when our users will select one of them within the Latest list, as we'll be able to point them to something similar to a detail page. It will also be very useful when we'll have to deal with CRUD operations such as Delete and Update.

We're not dealing with the client-side code yet, so we don't know how we'll present such a scenario to the user. However, we already know what we'll eventually need, a Get, Put, Post, and Delete method for each one of our entries--Quizzes, Questions, Answers, and Results--as we'll definitely have to perform these operations for all of them.

Luckily enough, we don't need to implement them now. However, since we're working with these Controllers, it can be a good time to set up a basic interface:

 #region RESTful conventions methods 
/// <summary> 
/// Retrieves the Answer with the given {id} 
/// </summary>