Suggestion: Using StrongName instead

[Tazer]

Should this be done ?

The problem is with: http://blogs.msdn.com/b/webdev/archive/2014/05/12/announcing-asp-net-session-state-provider-for-redis-preview-release.aspx also made an issue here: StackExchange/StackExchange.Redis#146

[TheCloudlessSky]

Thanks for bringing this to my attention!

I don't want to maintain two separate Nuget releases because it's a hack, confuses people and causes the double-package problem.

Even though I'm personally against strong naming (it should be deprecated all together), what should happen is StackExchange.Redis should not have two separate packages (because it causes problems like this). It forces every library that has a dependency on StackExchange.Redis to also have two separate libraries. If the library wants to support strong naming, it should just be a single library with a frozen assembly version. I'll leave this open and continue the discussion on StackExchange/StackExchange.Redis#146.

[TheCloudlessSky]

@Tazer I'm sure you're getting updates on the other issue, but right now without having to rebuild/change any libraries/dependencies, you can do the following in your project.

1. Right-click on the StackExchange.Redis.StrongName reference in your project(s) and click on Properties.
2. Change the Aliases to signed (remove global):

Because you don't need to use StackExchange.Redis directly when you configure Microsoft.Web.RedisSessionStateProvider, you can change its alias to anything other than global and this allows the project to compile/run. I just tested this with a fresh MVC4 project and it worked perfectly.

[Tazer]

Great, Thanks for the update. I did solve it in the meantime with a custom built version with StackExchange.Redis.StrongName as a Reference, But will use your suggestion when I have some time over

[Tazer]

But guess your comment would be great to have in the README.md ? :)

[TheCloudlessSky]

Yup - I've added a link back to this PR in the README. Thanks!

[dobryanskyy]

I have to use strong naming due to policy in my company. To be able to use this library i had to compile sources with my own key(as well as redis lib). Now i will not be able to use updates from this lib('cause they will not appear in my nuget and i'll miss them). Such a pity....

[TheCloudlessSky]

@dobryanskyy Your company needs to review it's policy because strong naming is not guaranteed and is not recommended for sandboxing anymore.

If you submit a PR that automatically does the strong naming, I'd be happy to include it for those that need it.

[TheCloudlessSky]

@dobryanskyy Have you seen this: https://github.com/dsplaisted/strongnamer

[dobryanskyy]

Yes, I've seen that. I even tried it. But for some reason - it crashed upon working on this package.