Book Image

Learning Angular for .NET Developers

By : Rajesh Gunasundaram
Book Image

Learning Angular for .NET Developers

By: Rajesh Gunasundaram

Overview of this book

Are you are looking for a better, more efficient, and more powerful way of building front-end web applications? Well, look no further, you have come to the right place! This book comprehensively integrates Angular version 4 into your tool belt, then runs you through all the new options you now have on hand for your web apps without bogging you down. The frameworks, tools, and libraries mentioned here will make your work productive and minimize the friction usually associated with building server-side web applications. Starting off with building blocks of Angular version 4, we gradually move into integrating TypeScript and ES6. You will get confident in building single page applications and using Angular for prototyping components. You will then move on to building web services and full-stack web application using ASP.NET WebAPI. Finally, you will learn the development process focused on rapid delivery and testability for all application layers.
Table of Contents (16 chapters)
Title Page
About the Author
About the Reviewers
Customer Feedback

Deployment options

There are four options for deployment. All the options are supported by the dotnet command-line interface. You can choose to copy over the app's project, let the DNX restore the packages, and run the app. A compatible DNX version has to be preinstalled; use the CLI command dotnet run for this one.

You can also let the CLI compile the project on your development machine. Copy over the assemblies and run:

Fig 08: Deployment Options

There is also the option to natively compile an app using a command-line switch. This means that instead of assemblies with IL, native binaries that can be directly executed without the help of the DNX or any .NET Framework are generated.

There is also an option to package your application into a NuGet package to easily share your project using dotnet pack. The package will contain support for all the configured frameworks in the project.json file. You can then upload it to a NuGet feed either globally or for your company only.

The final option is...