Visual Studio 2015 and Gulp Episode III: Assigning to a Build Step

This is the third post in a series about using Gulp with Visual Studio. If you missed the first post feel free to take the time to go back and read it Visual Studio 2015 CTP 6 and Gulp – Episode I: Getting Started or the second post Visual Studio 2015 CTP 6 and Gulp Episode II: First Task.

Great, now how can I use it?

You could run this from the console window by typing gulp javascript but we are using Visual Studio and have this fancy Task Runner Explorer we want to use. If you already had the Task Runner Explorer open you may have seen it change from this

Before

 

Task Runner Explorer before we created the javascript task

to this

After

Task Runner Explorer after we created the javascript task

when we created the javascript task.

If you did not go to your View -> Other Windows -> Task Runner Explorer to open it. Open Task Runner Explorer

Now you can see all the tasks you currently have set up, in this case just the one. To run it, right click and select run or double click it. This will open a window to the right of the available tasks and show the console output of the task you ran.

gulp task output in Task Runner Explorer

If you are following along at home you should now have a file in your wwwroot named app.js that looks like this.

document.addEventListener("DOMContentLoaded",function(){alert("This page loaded!")});  
document.addEventListener("DOMContentLoaded",function(){var e=2e3;window.setTimeout(function(){var e=document.getElementById(e);e.className+=" delayed"},e)});  

You may notice the lack of whitespace shortened variable names and removal off comments but it looks like it’s all there.

If you add a reference to app.js in your index page and run IIS, the page should load and alert you that “this page loaded!”

Conclude your epic journey with Visual Studio 2015 and Gulp Episode IV: The Styles.

Leave a Reply