-
Notifications
You must be signed in to change notification settings - Fork 110
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
Please update StrongName nuget package to same as non-signed one #73
Comments
+1, because Microsoft.AspNetCore.All => Microsoft.Extensions.Caching.Redis (2.0.1) => StackExchange.Redis.StrongName (1.2.4) |
The problem also occurs when using the A fix to this issue would be much appreciated. |
I think this update is important because of the backwards-incompatible nature of the SE.Redis update I talked about in #78 (comment) I'm on ASP.NET Core 2.1.x don't want to upgrade fully to SE.Redis 2.x yet, but I would like the fixes from the latest version of this package :) In the meantime, I am using this as a workaround (add it as a child beneath the
This fixes the build errors, but causes any file that has
If we are able to upgrade to the latest version of the strongname version of this package, the issue will go away completely. |
Update: I was able to fix this by referencing After I did that I had to add in a few dependencies I was missing that were in Anyone who uses SignalR, etc will still need that fix. |
subj, cant use non-strongname one because of Signalr.redis
The text was updated successfully, but these errors were encountered: