Gulp overview

15
Gulp
  • Upload

    -
  • Category

    Software

  • view

    339
  • download

    0

Transcript of Gulp overview

Page 1: Gulp overview

Gulp

Page 2: Gulp overview

Frontend Ecosystem overview

Page 3: Gulp overview

Frontend Ecosystem overview

Page 4: Gulp overview

Gulp basics

• Gulp is a tool for developers

• Write code, not configuration

• Concentrates on giving you little helpers called plugins supposed to do one and only one thing.

• There’s no “advanced” of gulp

• Gulp stays lean and provides very minimum to accomplish the task.

Page 5: Gulp overview

Gulpfile

• gulpfile.js is an entry point that will be reach when executing gulp commandName

Page 6: Gulp overview

streams

var fs = require("fs");

var readStream = fs.createReadStream("./file1.txt");

var writeStream = fs.createWriteStream("./output.txt")

readStream.pipe(writeStream);

readStream.pipe(process.stdout);

Page 8: Gulp overview

Visual Studio

• Task runner http://webtooling.visualstudio.com/task-runners/gulp/

• Web Essentials http://vswebessentials.com/

• Node JS tools https://www.visualstudio.com/en-us/features/node-js-vs.aspx

Page 9: Gulp overview

Node JS tools (extensions and updates)

Page 10: Gulp overview

NPM Scripts Task Runner

Page 11: Gulp overview

Npm/bower vs nugget

• Nuget is not designed for frontend packages.

• Npm and bower contains more packages.

Page 12: Gulp overview

ASP.NET trends

• The .NET ecosystem is migrating to the existing toolchains, instead of trying to roll their own.

• New versions of .NET are changing their task runners to use Gulp, and they are also switching to JSON-based configuration.

• .NET is aiming to become more portable. Using the tools provided by the frontend ecosystem (which is by nature platform-agnostic) makes sense in this regard.

• These tools are usable outside of the confines of .NET (as JS in the browser, again, has become its own system).

• You'll simply have more options in the long run (and, arguably, earlier).

Page 13: Gulp overview

Frontend in ASP.NET world

• ASP.NET bundles and minification is going to be deprecated

• Frontend development is no longer a subset of backend development

• Frontend is moving faster - much faster - than the equivalent tools in Visual Studio

Page 14: Gulp overview

Handling legacy

• Separate backend from frontend. Move to SPA app.

• Do not rely on platform features such as ASP.NET MVC bundles.

• Make your app backend agnostic.

Page 15: Gulp overview

Interesting info

• Introduction to ASP.NET 5 https://channel9.msdn.com/Events/Visual-Studio/Connect-event-2015/100

• https://github.com/aspnet/benchmarks