Merge pull request #10 from hotstone/master

Converted from MSTest to NUnit; removed Nuget package restore.
Merge pull request #11 from hotstone/master

Swallow exceptions when testing if a feature switch is on.
Issue #9 Add concrete examples to README.MD

Added examples for installing, configuring, initialising and using Femah
in the most basic scenarios.

There is a lot we can do to reduce down the installation steps using
native NuGet, for e.g.
- Step '2. Register the Femah HTTP handlers within your app' can use
config transformations to automatically add the HTTP handler
registrations, see
http://docs.nuget.org/docs/creating-packages/configuration-file-and-source-code-transformations
- Step '3. Initialise Femah within your app' can also use NuGet to copy
a default class with a predefined Enum to a specified location, see
http://stackoverflow.com/questions/10785596/can-nuget-add-a-cs-file-to-the-destination-project

Before implementing any of the above within the NuGet package
installation natively we could investigate bundling our own PowerShell
CmdLet/Module that would allow users to selectively configure their app
post NuGet Package installation (following our approach of being
un-intrusive to the host app).  Certainly not required for MVP but
thoughts?
Adding AssemblyInformationalVersion property
#6 Build script for Femah
#7 Publish Femah as a NuGet.org package
Added automated build scripting that..
- Cleans build folders
- Generates a consistent version number
- Compiles
- Executes NUnit unit tests
- Creates versioned (prerelease) Femah.Core NuGet package
Merge pull request #15 from lholman/master

#6 Build script for Femah and #7 Publish Femah as a NuGet.org package