-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Conversation
Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas |
Related: #109335. FYI @ViktorHofer |
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). |
For this package, yes. |
There was a problem hiding this 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.
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.
Submitted #109634 |
Closing in favor of #109634. |
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.
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