Test-Driving a NuGet package for MVC

To view this screencast, add it to your cart and checkout. You can buy this screencast for any price, including FREE!

When I’m working on my MVC sites, I often find myself wanting features that don’t come out of the box.

When I know I want a feature, my thought process tells me to:

  1. Search on Google/MSDN/StackOverflow to see if the feature is built into MVC
  2. Search on nuget.org for a NuGet package that has the feature
  3. Search on GitHub/Codeplex/Google Code for a project that has the feature
  4. Can’t find it anywhere? I guess it’s time to make it!

In this episode, we take a simple feature that I wish MVC had and implement it.

Before we start coding, we actually look for a matching library! I found one that’s close to what I want but, unfortunately, the author didn’t make his source control available so we had no way of easily contributing changes :(

After our tests are passing and the feature is implemented, we turn it into a NuGet package and publish it!

NOTE We do this on Linux using Mono. Clide is used to create our project. MooGet is used for NuGet support on Linux.

Resources