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

DIY versus framework-based styling


Now that we have converted all our static CSS files into dynamic LESS scripts, we can definitely take the chance to replace the quick'n'dirty styling that we put together for demonstration purposes, only with something better. However, before doing that, we need to choose which of these we want to do:

  1. Keep the Bootstrap framework that was shipped by our ASP.NET Core MVC with Angular template.
  2. Replace it with another frontend framework such as Foundation, Pure, Skeleton, UIKit, and Materialize.
  3. Remove it and also avoid any framework-based alternative, thus adopting a pure do-it-yourself approach.

The first two options share the same approach: leverage our styling on a consolidated environment used by thousands of developers; no matter which variant we'll choose, we'll end up walking on solid ground. The latter, however, is an entirely different pair of shoes. Anyone who is into CSS design is well aware of such a debate, which we can summarize in the following...