Check-point before I remove the ability for SpecsFor.Mvc to operate independently of SpecsFor.
Started adding support for customizable conventions into SpecsFor.Mvc.
FluentField now let's you assert off the value of a field in a fluent way.
You can now specify a custom temporary directory name for hosting your MVC app with SpecsFor.Mvc.  This makes it possible to run two sites at once.
Bumped NuGet package version.
Bumped version for final SpecsFor 4.2.0 release.
SpecsFor.Mvc now throws an exception if you forget to specify the browser to use.
SpecsFor.Mvc now provides a way to load in ASP.NET MVC attribute routing-based routes.
Completely changed how the Selenium WebDrivers are referenced.  This should ensure that newer versions of WebDriver are more easily accessible.
The SpecsFor.Mvc installation now checks for the required version of Microsoft Build Tools and displays an installation confirmation page.  If MS Build Tools is missing, the confirmation page includes instructions on correcting the issue.
SpecsFor.Mvc now uses Microsoft.Build.Utilities to locate the correct version of MSBuild to use, which should reduce the number of cases when the publish fails.

SpecsFor.Mvc now targets .NET 4.5.1.
SpecsFor.Mvc now throws an error if it cannot find MS Build Tools on the local machine.
Bumped version number for first RC release of 4.0 of SpecsFor.Mvc.
Upgraded packages, upgraded test projects to .NET 4.5.1, bumped version to 4.0.0-rc2.