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

Migrate to .NETStandard #9

Closed
kevinchalet opened this issue Mar 27, 2016 · 2 comments
Closed

Migrate to .NETStandard #9

kevinchalet opened this issue Mar 27, 2016 · 2 comments

Comments

@kevinchalet
Copy link

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)

https://github.com/henkmollema/CryptoHelper/blob/master/src/CryptoHelper/project.json#L29

Thanks!

/cc @henkmollema

@henkmollema
Copy link
Owner

Thanks for the heads up. I'll look into it asap. 👍

@kevinchalet
Copy link
Author

Closing, as this was fixed a while ago (3074747) 😄

Thanks 👏

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

2 participants