Book Image

ASP.NET Core and Angular 2

By : Valerio De Sanctis
Book Image

ASP.NET Core and Angular 2

By: Valerio De Sanctis

Overview of this book

<p>Writing code is about striking a balance between maintainability and productivity—how quickly you can write it against how much more you have to write in the future. This is a guide to doing just that by combining the impressive capabilities of ASP.NET Core and Angular 2. It shows you how to successfully manage an API and use it to support and power a dynamic single-page application.</p> <p>We'll show you how to construct your data model and manage routing and redirects before wrapping it up and styling it, all with the help of ASP.NET and Angular 2. You'll also learn how to optimize your application for SEO, check and secure any vulnerabilities, implement a viable authentication mechanism and, last but not least, use the proper tools and strategies for successful deployment. From readable URIs to OData retrieval and authentication patterns, we'll make sure you have all the technical knowledge you need and, more importantly, bring it all together so you can focus on what's important: a high-quality application that performs for users.</p>
Table of Contents (16 chapters)
ASP.NET Core and Angular 2
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Firing up the engine


It's time to publish our native web application. Before doing that, ensure that the Task Runner  default task is running, as we want to upload the latest version of our client files.

Right-click on the project's root node, then left-click on Publish. Select the Production-FTP profile and hit the Publish button to start the build and upload process.

The whole publishing process flow can be checked in real time within the Visual Studio Output window. As soon as the FTP connection will be attempted, we'll be asked for username and password, unless we gave our consent to store our login credentials within the Production-FTP.pubxml file.

The publishing task will require a lot more time than it used to be for ASP.NET 4 applications, because the whole set of ASP.NET Core libraries will be published in the destination folder, together with all the required Angular 2 modules and dependencies.

Tip

There's nothing to worry about, as this is another thing that will surely change once...