-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[release/9.0] [ILStrip] Fix passing assemblies using relative path #107548
Conversation
Tagging subscribers to this area: @directhex, @matouskozak |
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.
Approved.
CC @jeffschwMSFT. |
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.
approved. we can merge when ready
@carlossanlop, it is ready to merge. |
Backport of #107536 to release/9.0
/cc @jkurdek
Customer Impact
#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
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 forStripAssemblies
path anywhere.