-
Notifications
You must be signed in to change notification settings - Fork 519
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
ILStrip failed for ... resources.dll' not found #17009
Comments
Please attach a binary build log we can use to diagnose this, since #13922 is fixed and you're probably running into something different (although it looks the same). |
Hi @GioviQ. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
Thanks! For future self: the binlog named This is probably the underlying reason (note that the
This the input item:
I'm guessing we'll have to take TargetPath into account here: |
In the meanwhile how can I publish? |
@GioviQ adding this to your project file should do it: <PropertyGroup>
<EnableAssemblyILStripping>false</EnableAssemblyILStripping>
</PropertyGroup> |
This might be a dup of #14841. |
Just hit the same on 17.5.3, which among other issues adds to frustration. :( |
Any assembly that's not already on the Mac must be copied there, so do that. We detect if an assembly exist on the Mac by checking the file size of the file on Windows: a 0-length file is an output file from an assembly that exist on the Mac, otherwise it doesn't and must be copied. Fixes dotnet#17009. Fixes dotnet#14841. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1817898.
Any assembly that's not already on the Mac must be copied there, so do that. We detect if an assembly exist on the Mac by checking the file size of the file on Windows: a 0-length file is an output file from an assembly that exist on the Mac, otherwise it doesn't and must be copied. Fixes #17009. Fixes #14841. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1817898.
… Windows. Any assembly that's not already on the Mac must be copied there, so do that. We detect if an assembly exist on the Mac by checking the file size of the file on Windows: a 0-length file is an output file from an assembly that exist on the Mac, otherwise it doesn't and must be copied. Fixes dotnet#17009. Fixes dotnet#14841. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1817898. Backport of dotnet#18508.
… Windows. (#18511) Any assembly that's not already on the Mac must be copied there, so do that. We detect if an assembly exist on the Mac by checking the file size of the file on Windows: a 0-length file is an output file from an assembly that exist on the Mac, otherwise it doesn't and must be copied. Fixes #17009. Fixes #14841. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1817898. Backport of #18508.
Any assembly that's not already on the Mac must be copied there, so do that. We detect if an assembly exist on the Mac by checking the file size of the file on Windows: a 0-length file is an output file from an assembly that exist on the Mac, otherwise it doesn't and must be copied. Fixes dotnet#17009. Fixes dotnet#14841. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1817898.
I experience the same issue as #13922
Differences
MAUI net7.0-ios
Visual Studio 17.4.2
The text was updated successfully, but these errors were encountered: