Grunt.Js examination

Lately I have been looking at VS2015 / ASP vNext, and it did not take a genius to see that you need to know NPM/Bower and Gulp/Grunt. I have used NPM before and Bower is easy to pick up. I have not used (but have heard of) Gulp and Grunt before.

I looked at both of these over the past couple of weeks, and decided I liked Grunt better. For those that have not heard of Grunt it is a task runner for running repetitive tasks. There are lots of examples/resources available for Grunt, but I kind of wanted to look/try it myself. I have written up my findings in the following article.


Like I say this is nothing new, and I expect most web developers would be like, yeah obviously, it was however interesting for me as a grunt newbie, which others may be.



For a while now I have found myself becoming interested in CQRS, and I am fortunate enough to work with a practitioner of CQRS. As such it seemed like a good time to try and learn a bit more about this pattern.

I have created a small demo app that is a fully asynchronous CQRS example.

If this sounds like it may of interest to you, you can read more about it over at codeproject : CQRS : A Cross Examination Of How It Works


Git protocol errors when using Bower package manager

I have just got back from a month long holiday (which was great). Anyway back to work now…..sigh

So the other day I was trying to get Yeoman to scaffold a new angular.js app for me, which worked fine. I then wanted to use the Bower package manager to download a package, and whoever created the package hosted it on Git. Bower can deal with this just fine. But if like me your network is locked down, where there are all sorts of firewall/proxy rules, you may not be able to use the git protocol.

Luckily this is an easy fix, and all you need to do is issue this command line to have git add a configuration rule to re-write git urls to https

git config --global url."https://".insteadOf git://

What Changes Did This Command Make?

Take a look at your global configuration using:

git config --list

You’ll see the following line in the output:


You can see how this looks on file, by taking a peek at ~/.gitconfig where you should now see that the following two lines have been added:

[url "https://"]
    insteadOf = git://

And that is all there is to it, everything just worked after that.