Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StackExchange.Redis upgrading from 1.2.6 to 2.0.495 breaks RedLock.net #40

Closed
TomGullen opened this issue Sep 5, 2018 · 4 comments
Closed

Comments

@TomGullen
Copy link

Could not load file or assembly 'StackExchange.Redis, Version=1.1.608.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

New version of StackExchange.Redis jumps from 1.2.6 to 2.0.495 and this breaks RedLock.net

@samcook
Copy link
Owner

samcook commented Sep 5, 2018

Hmm, according to https://stackexchange.github.io/StackExchange.Redis/ReleaseNotes, the 2.0.495 version is a breaking change and will need recompilation.

2.0 is a large - and breaking - change

HARD BREAK: the package identity has changed; instead of StackExchange.Redis (not strong-named) and StackExchange.Redis.StrongName (strong-named), we are now only releasing StackExchange.Redis (strong-named). This is a binary breaking change that requires consumers to be re-compiled; it cannot be applied via binding-redirects.

I'll need to apply a maximum version constraint to the nuget package dependency for this. In the meantime, you'll need to stick with version 1.2.6 of StackExchange.Redis.

@TomGullen
Copy link
Author

Thanks for quick response, much appreciated!

@samcook
Copy link
Owner

samcook commented Sep 5, 2018

I've pushed out a non-prerelease version of 2.1.0 just now which also includes this nuget dependency constraint.

@samcook samcook closed this as completed Sep 5, 2018
@ghd258
Copy link

ghd258 commented Sep 25, 2018

Updated when StackExchange.Redis 2 is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants