-
Notifications
You must be signed in to change notification settings - Fork 424
Issue with ValueTuple on net471 #543
Comments
As I'm also victim of the ValueTuple problems and the Binding Warnings, this might help as it contains a repro for the binding warnings, dotnet/project-system#2905 |
I have an issue with 4.7.1 and ValueTuple too but it is a little bit different. I wanted to target my project to 4.7.1 but it doesn't build anymore. Here are the build errors:
I understand that is caused by having two references which hold ValueTuple type. The solution would be to uninstall ValueTuple NuGet package but I am not able to do it. I have references to other libraries targeting 4.6.2 and having dependences on ValueTuple NuGet package. Is there any workaround until the dependent packages are upgraded to 4.7.x too? |
@marisks are you using the latest version of the System.ValueTuple package? I would expect the latest one to typeforward the type down to mscorlib for net471 in order to avoid the conflicts. |
Now I have ValueTuple 4.4.0 installed. |
do you have a simple repro that I can take a look at? If not, then can you produce at least a binlog and share it? To produce a binlog simply build your project through the command line like: |
Is there any workaround for this? I just ran into it upgrading a project to .NET 472 with ValueTuple 4.5.0. Nearly a year later I would have assumed this has been fixed. |
Running into this as well, I have ValueTuple 4.5.0 (the latest), which I can't uninstall because I'm using a library that targets 4.6 (Automapper). Getting this error after trying to target 4.7.2. I'm not able to paste the entire binlog, but I pulled out all the parts that mention ValueTuple:
long resgen line contains this flag
long csc line contains this flag
|
There are some workarounds at the bottom of this issue: seesharper/LightInject#447 I used |
I believe this issue is a duplicate of many others we've been seeing related to binding redirects - see https://github.com/dotnet/corefx/issues/32561#issuecomment-428138193 for a list of relevant issues where you should be able to find guidance on how to work around it. |
@terrajobst @ryanelian If it's ok, let's move the investigation to a dedicated issue.
Here's the latest comment from Ryan, in the thread for #514.
msbuild.zip
btw, just curious, how do you 'see' the content of the binary log?
No, adding those lines does not make the warning message disappear...
The text was updated successfully, but these errors were encountered: