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

Reference net10.0 path for ILLink.Tasks assembly #109619

Closed
wants to merge 1 commit into from

Conversation

mthalman
Copy link
Member

@mthalman mthalman commented Nov 7, 2024

ILLink.Tasks targets the net10.0 TFM and it needs the assembly reference for the MSBuild props file to match that TFM.

Related to dotnet/sdk#44685

@mthalman mthalman requested a review from sbomer as a code owner November 7, 2024 18:44
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-Tools-ILLink .NET linker development as well as trimming analyzers label Nov 7, 2024
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Nov 7, 2024
Copy link
Contributor

Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas
See info in area-owners.md if you want to be subscribed.

@sbomer
Copy link
Member

sbomer commented Nov 7, 2024

Related: #109335. FYI @ViktorHofer

@ViktorHofer
Copy link
Member

This change can't be made as is. Illink in this repo still targets net9.0. I think it would be better to avoid the TFM version in the folder path entirely.

@am11
Copy link
Member

am11 commented Nov 8, 2024

This change can't be made as is. Illink in this repo still targets net9.0. I think it would be better to avoid the TFM version in the folder path entirely.

+1 (assuming that for a given task package, there's always only a single implementation assembly).

@ViktorHofer
Copy link
Member

For this package, yes.

Copy link
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

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

This change can't be made because runtime still targets net9.0.

ViktorHofer added a commit that referenced this pull request Nov 8, 2024
Replaces #109619

We made a similar change recently in arcade to not use the TFM but a normalized value of the TargetFrameworkIdentifier property for tools packages.
@ViktorHofer
Copy link
Member

Submitted #109634

@mthalman
Copy link
Member Author

mthalman commented Nov 8, 2024

Closing in favor of #109634.

@mthalman mthalman closed this Nov 8, 2024
akoeplinger pushed a commit that referenced this pull request Nov 8, 2024
Replaces #109619

We made a similar change recently in arcade to not use the TFM but a normalized value of the TargetFrameworkIdentifier property for tools packages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Tools-ILLink .NET linker development as well as trimming analyzers linkable-framework Issues associated with delivering a linker friendly framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants