Michael Denny

I know that could sound useless this configuration, because leaving the connection and subscription auto healing is cool, but if you were the guy that relies on the current behavior...

I was reading again the wiki, and I'm curious to go back in time on the source code, and see what was the behavior when the wiki was written, because...

ok @AlistairClark7 I had time to digging deeper on this, and I found that the current version of ENQ **works as expected when you specify `timeout=0`**, when no timeout is...

Anyway if you're working on the PR, I would like to see it, because I would like to leave an open discussion on this

> Is autodelete blocking this? yes, this will cause the consumer to be explicitly canceled by the broker (rabbitmq), so is the same as if you were deleting a queue...

> This is intended as fix for #150 ok now make sense 😄 you can add in the description of the PR "fixes #150" so the issue will be closed...

Check the build error, there's something: > C:\projects\easynetq-management-client\Source\EasyNetQ.Management.Client.IntegrationTests\ManagementClientTests.cs(81,39): error CS1061: 'StringCollectionAssertions' does not contain a definition for 'Be' and no accessible extension method 'Be' accepting a first argument of type...

`WebUtility` is present in [.netstandard 1.5](https://docs.microsoft.com/en-us/dotnet/api/system.net.webutility?view=netstandard-1.5) and [netfx 4.5.2](https://docs.microsoft.com/en-us/dotnet/api/system.net.webutility?view=netframework-4.5.2) so I think would be great to use it and fix all possible characters. what do you think @mijabr @zidad ?

> WebUtility.UrlEncode(....); @mijabr can you apply that method instead of all the replace?

@mijabr can we do this for all the methods? so we cover all the management api