React to the new StackExchange.Redis v2.0 package

[oerodriguezn]

Please update Microsoft.AspNetCore.DataProtection.Redis to use Redis.StackExchange 2.0 where there is no more a StackExchange.Redis.StrongName.

https://stackexchange.github.io/StackExchange.Redis/ReleaseNotes

[ghd258]

Microsoft.Extensions.Caching.Redis update StackExchange.Redis 2.0

[blowdart]

@natemcmaster One for 2.1

[Tratcher]

Nope, it's a major break. See aspnet/Caching#410

[Eilon]

Thanks @Tratcher I just commented on aspnet/Caching#410 (comment).

We can solve this in many places by shipping a new package (with a new name) that has the new dependency and new APIs to enable it. Apps would have to opt-in to this. We could, if we wanted to, also release a 2.1 compatible package. That might be reasonable given that 2.1 is LTS.

[muratg]

We'll be creating a new package: Microsoft.AspNetCore.DataProtection.StackExchangeRedis which uses that.

cc @anurse @Tratcher @DamianEdwards @Eilon

[sereeth]

Sigh. Well, this issue has us dead in the water as Hangfire.Pro.Redis brings in StackExchange.Redis (not strongly named), and Microsoft.AspNetCore.DataProduction.Redis brings in the strong named version. How do people get around this incredibly frustrating issue? For the love of Pete, all we were trying to do was use the ConnectionMultiplexer.

[Eilon]

We are updating DataProtection.Redis to use the strong-named StackExchange Redis package. Once we have that published, are you still anticipating an issue?

[BrennanConroy]

This has been merged aspnet/DataProtection#325