Proper disposal of MD5CryptoServiceProvider
Added support to remove deferred messages on saga completion to ActiveMQ Transport
Added custom ActiveMQ assemblies and changed transaction handling to receive messages in an ambient transaction in case of DTC
Enabled Transaction Acceptance Tests for ActiveMQ
Merge branch 'develop' of git://github.com/NServiceBus/NServiceBus into develop

Conflicts:
	AcceptanceTests/NServiceBus.AcceptanceTests/Transactions/When_receiving_a_message_with_dtc_disabled.cs
Changed assembly references to custom ActiveMQ.NMS Assemblies in the Integration tests
Adding tests to verify that all transports behave correctly when the
endpoint is non transactional
Added tests that verifies that the transports enlist in the ambient tx
even if the transport in non transactional
partitionkey and catchup interval now configurable for timeoutpersister
split azure message queue sender & receiver into separate files
Merge branch 'develop' of https://github.com/NServiceBus/NServiceBus into develop
The rabbit mq transport now used the default "amq.topic" exchange for
pubsub. This removed the need for any configuration for pubsub to work
We now supports autosubscribe without needing config for the transports
that provide centralized pub/sub with topic (like RabbitMq and ActiveMq)
implemented batching support for azure servicebus
- Replaced Apache.NMS.ActiveMQ.dll custom assemblies by new ones that allow to configure the DTC ResourceManagerId.
- Changed connection string to make ResourceManagerId configurable

Without this it is not possible to connect multiple endpoints to the same AMQ server instance because the broker id was used as resource manager id
Changed that DTCTransactionSessionFactory only returns the session of the message consumer if a publish is in the same transaction.
Merge branch 'develop' of github.com:NServiceBus/NServiceBus into develop
Changed activemq connection string to match new syntax
Improved Apache.NMS.ActiveMQ assembly to be more robust in case of exceptions. Mutexes were abandoned before.
Changed When_receiving_a_message_with_dtc_disabled Should_not_escalate_a_single_durable_rm_to_dtc_tx to configure transaction settings before transport.
ActiveMQ requires these informations during transport configuration because it influences the components used to create the transport.