Expanding message registration exception message as it is a little misleading

The exception message states that the messages must implement, IMessage, IEvent or ICommand however this may not have been the cause of the exception. If the user has configured NSB such that the message types have never been registered (e.g. NSB has not scanned the required assembly) then they will also get this error message even though their messages implement the correct interfaces.
messing with a behavior pipeline or a chain or a Russian doll or whatever
small adjustments
Modified the spike to show how a user can build a UoW and how it would
lean on the child container to pass the session. For other internal
behaviours I'd say we should use the context.Set() instead. I also think
we need a Get|Set(string) since we need to add eg the message and saga
data and we need to get access to it without knowing the type
Fixed the problem: when FRM attribute was present, instead of adding a commented out section for the AuditConfig, a section element was added, resulting in startup error.
Removing the setup files since there is a new repo for them
Disabled a unstable test until we can find the root cause
http://builds.particular.net/viewLog.html?buildId=24968&tab=buildResultsDiv&buildTypeId=NServiceBusCore_Build#testNameId3699571671064821291
Added nuspec for tools nuget
fix build release configuration update
Added missing T4Scaffolding.Core nuget dep to host package.
Added src to package
move to versioning before build

fixes #1639
add missing file
fix #1635
Changed the DefaultFloatConstraint to Current
Updating ripple to suport codeonly packages
Updated readme with up to date build instructions
Merge branch 'release-4.1.0' into develop
Removed buid.bat
Updated returntosourcequeue to look at the new v4 headers, closes #1640