#69 - API returns HTTP 204 from all PUT requests. Enabling some unit tests again and tweaking a comparison in the ApiResponseBuilder
#69 - API always returns 304 as response from PUT request.
Modified the InProcProvider initialisation to set a fully qualified assembly name, made similar change to Femah.Core.Femah.SetSwitchType
Merge pull request #79 from lholman/69-api-returns-304-from-put

#69 - API always returns 304 as response from PUT request
Moved tests for IsFeatureOn into sub class
Factored out repeated provider mock creation code
Merge remote-tracking branch 'awanoodle/UpdateFemahTests'
#69 - API always returns 304 as response from PUT request. Modifying the PUT request to return just an HTTP statuscode of 304 with no body if there are no changes.
Merge branch '69-api-return-statuscode-only-with-304'
#48 - Add release notes to Femah.Core NuGet package when publishing.
- Modified the existing build to utilise psake https://github.com/psake/psake/. This provides a task orientated build process better suited to the more involved deployment pipeline automation now required as discussed in #48.
Merge branch '48-include-psake-in-femah-build'
Factored out recurring code to create a feature switch
IsOnIffRandomNumberBelowThreshold changed to use TestCase data rather than multiple cases in one test
Changed names to fit with more BDD style
Split out UsesValueFromCookieWhenCookieExists to be seperate tests
Switched to using the NUnit Result field in the TestCase attribute
Removed unused remoting include
Set test case names for cookie tests
Added test case names for percentage threshold tests
Merge branch 'MovingPercentageFeatureSwitchTests' of https://github.com/AwaNoodle/femah into MovingPercentageFeatureSwitchTests

Conflicts:
	Femah.Core.Tests/PercentageFeatureSwitchTests.cs