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

Proper way to refer to IdentityModel2 in a .netstandared2.0 library. #49

Closed
weliwita opened this issue Jun 1, 2017 · 2 comments
Closed
Labels

Comments

@weliwita
Copy link

weliwita commented Jun 1, 2017

This issue is related to this StackOverflow question. https://stackoverflow.com/questions/44211741/how-to-resolve-httpclient-exists-in-multiple-libs/44299428.

We need to refer IdentityModel library which is targeting .netstandared1.4 from our library targeting .netstandared2.0. But we also refer to HttpClient in our library as well. Ideally .netstandared1.4 targeted library is callable from higher version targeted library. But IdentityModel also references System.Net.Http outside of the standard library. So we ended up with 2 HttpClients and failed to build our project. What is the proper way to fix this? Should we wait until newer version targeting .netstandared2.0?

@leastprivilege
Copy link
Contributor

I actually don't know - we had various problem reports because of that.

Maybe open an issue on the dotnet repo asking for right way to deal with HttpClient. Would be interested in the result.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

2 participants