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

Does this work in .NET Core 2.0? #66

Open
tlanzer opened this issue Jan 23, 2018 · 5 comments
Open

Does this work in .NET Core 2.0? #66

tlanzer opened this issue Jan 23, 2018 · 5 comments

Comments

@tlanzer
Copy link

tlanzer commented Jan 23, 2018

This package won't install for me into a .NET Core 2.0 project in VS 2017. Is this known. I just get a vague "The given key was not present in the dictionary." error.

@stefann42
Copy link
Member

stefann42 commented Jan 23, 2018

Current version of the package targets .NET Framework 4.5 - 4.7 and doesn't not work with .NET Core 2.0. We're working on adding support for .NET Core.

@tlanzer
Copy link
Author

tlanzer commented Jan 23, 2018

FYI, after reading about the Nuget issues in the VS 15.4 update which were fixed in 15.5 (https://developercommunity.visualstudio.com/content/problem/128974/error-occured-while-restoring-nuget-packages-1.html), I updated my VS to 15.5 and my error went away. Thanks for letting me know it doesn't support .NET Core, though.

@stefann42
Copy link
Member

@ElvenMonky here's a discussion from another library for how they evolved their package to support .NET Core jwt-dotnet/jwt#72. We should do something similar.

@ElvenMonky
Copy link
Collaborator

Isn't it a duplicate of #20? @tonysurma's repo follows this approach with slightly better backwards compatibility (.Net Standard 1.1 is compatible with .Net Framework 4.5 and VS 2013). Support of VS 2012 will be dropped anyway, but I think it's ok.

@mikelor
Copy link

mikelor commented Jun 12, 2018

What's the likelihood of updating this to .Net Standard 2.0. I've updated this so I can start using it in .Net Core Azure Functions.

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

No branches or pull requests

4 participants