You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CryptoHelper is currently targeting dotnet5.4 which is being replaced by netstandard1.3 everywhere, including the ASP.NET Core and aspnet-contrib projects. That would be great if CryptoHelper could be updated to use the new TFM (no hurries, of course, since we can use the imports section to make dotnet5.4 compatible with netstandard1.3).
Pushing a new build would also fix the weird assembly version issues we're seeing with DNX. Here's more context: openiddict/openiddict-core#76 (comment) (it's about IdentityModel, but CryptoHelper is similarly impacted)
CryptoHelper is currently targeting
dotnet5.4
which is being replaced bynetstandard1.3
everywhere, including the ASP.NET Core and aspnet-contrib projects. That would be great if CryptoHelper could be updated to use the new TFM (no hurries, of course, since we can use theimports
section to makedotnet5.4
compatible withnetstandard1.3
).Pushing a new build would also fix the weird assembly version issues we're seeing with DNX. Here's more context: openiddict/openiddict-core#76 (comment) (it's about IdentityModel, but CryptoHelper is similarly impacted)
https://github.com/henkmollema/CryptoHelper/blob/master/src/CryptoHelper/project.json#L29
Thanks!
/cc @henkmollema
The text was updated successfully, but these errors were encountered: