While I was following Azure documentation for how to use Redis Cache in Azure Portal I noticed this note:
If you prefer to use a strong-named version of t
Aside from the signed vs unsigned assemblies argument, the RedisSessionStateProvider has a dependency on StackExchange.Redis.StrongName
So if you want to use RedisSessionStateProvider, choose the StrongName version unless you want to have two dependencies.
Update: As @Matei_Radu has pointed out, Microsoft.AspNet.SignalR.Redis also has a dependency on StackExchange.Redis.StrongName
You can only have a dependency on one (either signed or unsigned) in a single assembly, but if you have multiple projects, you might have dependencies on both. It may simplify things to keep only the signed version to avoid problems