incorrect auth throws system.io.IOException

[deepakverma]

After updating to the latest NuGet package 1.0.297 in case of an incorrect authentication, I have started seeing the following exception been thrown, instead of the unabletoconnect exception "It was not possible to connect to the redis server(s)"
An unhandled exception of type 'System.IO.IOException' occurred in System.dll

Additional information: Unable to read data from the transport connection: Cannot access a disposed object.

Object name: 'System.Net.Sockets.Socket'..

[ppanyukov]

I've tested this fix with our setup of: Asp.net, Azure Redis Cache, SSL, wrong key (password);

• Nuget package 1.0.322 (prior to this fix) -> crashes w3wp.exe process, eventually leading to 503 Service Unavailable;
• Nuget package 1.0.333 (with this fix) -> resolves the problem, cannot reproduce any more. Correctly reports "Unable to connect", no more crashes.

So this works :)

[worldspawn]

I get this using 1.0.371

A first chance exception of type 'System.ObjectDisposedException' occurred in System.dll
Additional information: Cannot access a disposed object.

Connection string is just "host,password=password". I can't get past the Connect call. I'm also Azure Redis Cache... I am using the primary key provided as the password... though I can't find any documentation that explicitly states the primary key is the password (thanks MS).

Edit - password was wrong, was missing a bit of it.