Book Image

ASP.NET Core MVC 2.0 Cookbook

By : Jason De Oliveira, Engin Polat, Stephane Belkheraz
Book Image

ASP.NET Core MVC 2.0 Cookbook

By: Jason De Oliveira, Engin Polat, Stephane Belkheraz

Overview of this book

The ASP.NET Core 2.0 Framework has been designed to meet all the needs of today’s web developers. It provides better control, support for test-driven development, and cleaner code. Moreover, it’s lightweight and allows you to run apps on Windows, OSX and Linux, making it the most popular web framework with modern day developers. This book takes a unique approach to web development, using real-world examples to guide you through problems with ASP.NET Core 2.0 web applications. It covers Visual Studio 2017- and ASP.NET Core 2.0-specifc changes and provides general MVC development recipes. It explores setting up .NET Core, Visual Studio 2017, Node.js modules, and NuGet. Next, it shows you how to work with Inversion of Control data pattern and caching. We explore everyday ASP.NET Core MVC 2.0 patterns and go beyond it into troubleshooting. Finally, we lead you through migrating, hosting, and deploying your code. By the end of the book, you’ll not only have explored every aspect of ASP.NET Core MVC 2.0, you’ll also have a reference you can keep coming back to whenever you need to get the job done.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Introduction


In this chapter, we will learn about Node.js, Node modules, package managers, and task runners. With ASP.NET Core, we have different options to manage packages: NuGet, node package manager (npm), Bower, and JSPM. Most of the time, NuGet is used to manage .NET packages for server-side libraries, but it doesn't have to be used. We will cover NuGet in the next chapter. npm manages the JavaScript packages and modules for Node.js. Bower handles frontend dependencies (such as JavaScript, CSS, and other stuff, such as fonts). JSPM does the same as Bower, but also loads and compiles JavaScript files as AMD modules at runtime.

In this chapter, we will explore all these ways of managing client-side dependencies and how to use the two most famous task runners in the Node.js world, namely Grunt and Gulp.