We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

What do you mean “a front-end build pipeline”!

Formal Metadata

Title
What do you mean “a front-end build pipeline”!
Title of Series
Number of Parts
133
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
For quite some time, webdevelopers outside of the .NET space have been using tools to handle their front end resources in a better way, by using task runners and things like that. Until now, most .NET devs have left that up to Visual Studio and ASP.NET. At least if we generalize a little. However, with the release of ASP.NET 5, those features are being removed from Visual Studio, and replaced by native Node and Gulp/Grunt integration, something that will change the way we build things on the web in the future. Are you feeling a little unsure of what this means? Not 100% sure what Gulp and Grunt is? Feeling a little lost when people start talking about Node, npm and Bower? Why not go to this talk and get an understanding of the fundamentals of this new process presented to you in a quick way?