SyncOMatic update
Merge pull request #1996 from Particular/SyncOMatic-20140305-052836

SyncOMatic update
not all channels require deduplication
restoring timestamp target
making memory stream buffer accessible as azure servicebus internals seems to access it
Splitted gateway factory from gateway registry function, and made sure all parts are in the ioc
fixed container registration and stupid mistake in channel registry lookup
Let the exception bubble through appdomains
Abort the startup if we encounter a assembly scanning error
Fix typo 'make sure' was repeated
Merge pull request #1994 from Particular/issue-1993

Implement new license behavior. Fixes #1993
make x86 and anycpu projects first class projects

avoids the inner msbuild hack
Removed throttling / falling back to basic licensing mode if license expires. Fixes #1991
A byte does not support arithmetic.

See http://stackoverflow.com/a/941627/90882 for reasons why a byte does not support arithmetic.

This was causing the acceptance test to fail in certain circumstances.
Here is the error that could happen:
System.Runtime.Serialization.SerializationException: An error occurred while attempting to extract logical messages from transport message NServiceBus.TransportMessage ---> System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at NServiceBus.Serializers.XML.XmlMessageSerializer.Deserialize(Stream stream, IList`1 messageTypesToDeserialize) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Serializers\XML\XmlMessageSerializer.cs:line 292
   at NServiceBus.Unicast.Messages.ExtractLogicalMessagesBehavior.Extract(TransportMessage physicalMessage) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Unicast\Messages\ExtractLogicalMessagesBehavior.cs:line 74
   at NServiceBus.Unicast.Messages.ExtractLogicalMessagesBehavior.Invoke(ReceivePhysicalMessageContext context, Action next) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Unicast\Messages\ExtractLogicalMessagesBehavior.cs:line 52
   --- End of inner exception stack trace ---
   at NServiceBus.Unicast.Messages.ExtractLogicalMessagesBehavior.Invoke(ReceivePhysicalMessageContext context, Action next) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Unicast\Messages\ExtractLogicalMessagesBehavior.cs:line 58
   at NServiceBus.Sagas.RemoveIncomingHeadersBehavior.Invoke(ReceivePhysicalMessageContext context, Action next) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Sagas\RemoveIncomingHeadersBehavior.cs:line 23
   at NServiceBus.MessageMutator.ApplyIncomingTransportMessageMutatorsBehavior.Invoke(ReceivePhysicalMessageContext context, Action next) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\MessageMutator\ApplyIncomingTransportMessageMutatorsBehavior.cs:line 22
   at NServiceBus.UnitOfWork.UnitOfWorkBehavior.Invoke(ReceivePhysicalMessageContext context, Action next) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\UnitOfWork\UnitOfWorkBehavior.cs:line 24/n/r

This error was occurring in the SqlTransport, my guess is that by doing the arithmetic on the byte we were create a byte that was outside the range of valid bytes that SqlServer can serialize.
Making code inspector happy
It doesn't look like our agents know ToolsVersion="12.0"
Updating nuget project names
Merge pull request #1997 from superlogical/fix/develop/typo

Fix typo 'make sure' was repeated
Merge pull request #1937 from Particular/Issue_1937

Abort the startup if we encounter a assembly scanning error
Merge pull request #1998 from Particular/issue-1991

Removed throttling / falling back to basic licensing mode when license expires