Closed kooshan closed 5 years ago
I haven't tested out to adopt the library using any previews of .net core 2.2 I will try to play around with it when I have time.
But if you are keen to use the library using the preview of .net core 2.2, you can help me out by trying to pin point the issue, this library is compatible with .net standard 1.6 And a list of dependencies, not sure if one of them is not compatible with .net standard 2.1 or .net core 2.2.
Thanks for the quick answer. According to the dependencies I don't see anything causing this issue except the referenced IdentityServer4 version
<PackageReference Include="IdentityServer4" Version="1.0.0" />
Would increasing that to a later version like 2.2.0 break anything? Actually that would mandate an elevation to .netstandard2.0 and Newtonsoft.Json version >= '11.0.2'.
It compiles with a bunch of warnings. I would take some time to check for runtime errors as soon as I can find some spare time.
I'm willing to upgrade the library targeting .net standard 2 once Identity Server 4 v 2.3 is released.
One of the things looking forward to is to start relying on StackExchange.Redis v 2, which introduces pipelining that requires .net standard 2 at least.
but for the time being, I will keep the current release of the library compatible with Identity server 4 v 1.0.0 for all the customers who are still relying on that and not willing to upgrade.
Fine! thanks. I guess I have to go with commenting out the caching and wait.
Hi @kooshan
I may found the cause of the error, because Identity Server 4 team introduced this new library : IdentityServer4.Storage
Which is a breaking change, the current implementation of IdentityServer4.Contrib.RedisStore
will not work because the interfaces the library relies on are not in IdentityServer4
nuget package anymore, I need to work on that soon.
@kooshan Please do verify that this preview release solves your problem
I have the same issue with dotnet core 2.0 and dentityServer4.Contrib.RedisStore 2.0.0 :(
@Hub24Amir Can you elaborate more ? or provide a code to reproduce ? else I will not be able to help
Thanks for quick response. i guess situation is similar to what Kooshan mentioned however i just want to add using ver 2.0 didnt solve the issue. previously you asked Kooshan if ver 2 preview release does solve the issue. Thanks
Can you share more about your current setup, nuget packages version .. etc
Dont worry. It's not important anymore. Thanks for your help.
Hi, I encountered this issue a while ago and I finally narrowed it down to this package reference
If I comment that out and dismiss the redis cache API calls everything builds flawlessly.