and there was auditing of handled messages... now on to published messages
since we're in a handler, and queue interaction is transactional, we should not handle exceptions
added another test case for auditing of published messages
added Rabbit audit test cases
audit of published message seems to work now
added test to verify that published message is audited only once
the usual
can't include input queue in audit message when the publisher is a one-way client
Merge branch 'master' into feature-audit

Conflicts:
	src/.nuget/NuGet.exe
	src/.nuget/NuGet.targets
	src/Rebus.Tests/Rebus.Tests.csproj
	src/Rebus.Tests/Transports/Rabbit/RabbitMqFixtureBase.cs
	src/Rebus.sln
	src/Rebus/Bus/RebusBus.cs
	src/Rebus/Bus/RebusRouting.cs
	src/Rebus/Configuration/ConfigureAdditionalBehavior.cs
	src/Rebus/Configuration/RebusBehaviorConfigurer.cs
	src/Rebus/Transports/Msmq/MsmqMessageQueue.cs
minor tweaks
updated changelog
small modifications
Fix invalid logging call, which may fatally fail under some logging implementations.
Avoid creation of an useless queue named as our public exchange, when using an exchange as our public facing address.
Use InputQueueAddress (instead of InputQueue) during timeout manager  setup.
Fix SendLocal so it uses InputQueueAddress instead of InputQueue.
Added (initial) hability to send messages to either queues or exchanges (with & without specific routing key) to RabbitMQ trandsport.
updated changelog
Allow multiple sagas activated by same message for SQL server

https://github.com/rebus-org/Rebus/issues/126
Merge pull request #239 from PeteProgrammer/master

Allow multiple sagas activated by same message for SQL server