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

Client-side routing


Our Master/Detail relationship is indeed working, yet it has some major flaws. The current in-page navigation approach, for example, is completely different from the original plan. We wanted our users to switch back and forth between the HomeView containing the list of quizzes and a dedicated QuizView whenever he selects one of them, but the app doesn't do that; it just opens something like a "quiz detail panel" under each list. Not just one but three different panels, one for each item lists--that doesn’t make any sense! We need to fix that as soon as possible.

While doing that, we also have another issue to solve. You may have noted that, regardless of what we do within our app, the URL in the browser's address bar is always the same. It will mean that we won’t be able to share, say, a URL that will directly lead to a specific quiz; we’ll be forced to share the starting URL because it is the only supported one.

Wait a minute, isn’t this our Native Web application’s most...