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

[release/9.0] [ILStrip] Fix passing assemblies using relative path #107548

Merged
merged 2 commits into from
Sep 12, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 9, 2024

Backport of #107536 to release/9.0

/cc @jkurdek

Customer Impact

  • Customer reported
  • Found internally

#101967 Customer experienced compilation errors when referencing Cosmos DB nuget. Referencing this nuget caused unmanaged dlls to be referenced and passed to the ILStrip task which then crashed.

#106267 allowed ILStrip to gracefully handle (skip) unmanaged assemblies. Part of the fix included surfacing a new task output UpdatedAssemblies. This output is intended to be used by xamarin-macios in its MobileILStrip task.

While completing the fix on xamarin-macios side we have discovered that the UpdatedAssemblies output is not populated when assemblies are passed using relative paths, which caused some of the xamarin-macios tests to fail. This PR solves this issue. The fix is structured in a way to only affect the scenario enabled by #106267. It should not have any effect on other ILStrip applications.

Regression

  • Yes
  • No

Testing

The output is only to be used by xamarin-macios. The changes were verified locally by injecting a dll containing modified ILStrip into xamarin-macios.

Risk

(Very) Low. This change only affects UpdatedAssemblies output which is currently not used for StripAssemblies path anywhere.

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Sep 9, 2024
@jkurdek jkurdek added area-Infrastructure-mono os-ios Apple iOS and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Sep 9, 2024
Copy link
Contributor

Tagging subscribers to this area: @directhex, @matouskozak
See info in area-owners.md if you want to be subscribed.

@jkurdek jkurdek self-assigned this Sep 9, 2024
Copy link
Member

@JulieLeeMSFT JulieLeeMSFT left a comment

Choose a reason for hiding this comment

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

Approved.

@JulieLeeMSFT JulieLeeMSFT added the Servicing-approved Approved for servicing release label Sep 10, 2024
@JulieLeeMSFT
Copy link
Member

CC @jeffschwMSFT.

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

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

approved. we can merge when ready

@JulieLeeMSFT
Copy link
Member

@carlossanlop, it is ready to merge.

@jeffschwMSFT jeffschwMSFT merged commit c13aac8 into release/9.0 Sep 12, 2024
10 of 13 checks passed
@jkotas jkotas deleted the backport/pr-107536-to-release/9.0 branch September 18, 2024 21:32
@github-actions github-actions bot locked and limited conversation to collaborators Oct 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-mono os-ios Apple iOS Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants