-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
System.ValueTuple conflict #182
Comments
I do not see 4.0.1.0 version in NuGet https://www.nuget.org/packages/System.ValueTuple/ Probably it is unlisted and can be used. |
Looks like System.ValueTuple conflicts with itself |
Repro.zip |
Probably you just need to update System.ValueTuple 4.3.0 to 4.5.0 in Theraot.Core to resolve this |
And if I set |
Or downgrade to 4.0.1.0 |
"System.ValueTuple, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" is assembly for netstandart (strange version number and it has the same PublicKeyToken) |
It could be possible to downgrade the required package version in Vanara. |
@OwnageIsMagic The fix is merged into Vanara library. |
@NN--- now I have 2 libs with ValueTuple 4.3.0 and 5 with 4.5.0 in my dependency graph |
Seems like you have inevitable conflict. Simply add System.ValueTuple 4.5.0 package reference to your project. |
this doesn't work |
warning MSB3268: The primary reference "Quartz.dll" could not be resolved because it has an indirect dependency on the framework assembly "System.ValueTuple, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0". To resolve this problem, either remove the reference "Quartz.dll" or retarget your application to a framework version which contains "System.ValueTuple, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51".
due to dependency on System.ValueTuple 4.3.0 in Theraot.Core (3.2.11)
if I add System.ValueTuple 4.5.0 nuget package to the project this error goes away
The text was updated successfully, but these errors were encountered: