Skip to content

Alternative solution for ValueTuple conflicts *NO MERGE*#253

Closed
ericstj wants to merge 1 commit intodotnet:mainfrom
ericstj:valueTupleMoreSpecificVersion
Closed

Alternative solution for ValueTuple conflicts *NO MERGE*#253
ericstj wants to merge 1 commit intodotnet:mainfrom
ericstj:valueTupleMoreSpecificVersion

Conversation

@ericstj
Copy link
Copy Markdown
Member

@ericstj ericstj commented Feb 6, 2026

No description provided.

@ericstj ericstj marked this pull request as draft February 6, 2026 23:49
<ItemGroup>
<Reference Include="System.ValueTuple" SpecificVersion="true" />
<!-- We cannot have more than one primary reference, since others might resolve to the lower versioned framework assembly and the conflict will persist.-->
<Reference Remove="System.ValueTuple" />
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is most likely an incomplete solution. To be more fool-proof we should have a target that can remove all possible primary references (path, simple-name, strong-name) and run it right before RAR.

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

Successfully merging this pull request may close these issues.

1 participant