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

Full-scale test


We can't possibly say that we were slacking off here! After a tremendous amount of work, it's time to perform a final client-server test to ensure that everything is working as expected.

Note

Just a quick consideration before we start: it's been a while from our last client-server test, and we changed a whole lot of things. It's very important to understand that receiving some compiler, runtime, or GUI-related errors here will be perfectly normal, especially if we performed some find-replace as we did (not) suggest to. Whenever this happens, it will only mean that we missed something on the way. Don't lose the grip, read the error messages, use the built-in debugger, check up your source code, and do your best to find the issue; if you can't figure it out, try to "unmount" some component by removing the references; this will greatly help you understand what's actually working and where the problem lies. Always keep in mind that the code is never wrong, yet also don't forget...