-
Notifications
You must be signed in to change notification settings - Fork 601
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
fix: include native libraries when publishing executable #97
Conversation
This change is from Kyome22#97, which hopefully fixes Kyome22#96 and Kyome22#73
Sorry I'm not familiar with publishing of .NET, am I supposed to modify dotnet publish -p:PublishProfile=PublishWithDotNetProdile.pubxml it porduced executable along with several DLLs. Then I added |
I think modifying |
To be specific, yes, but I think it really doesn't matter where the option to be included. Framework-dependent builds will not change its behaviors whether the option is on or not. |
Oh, I mean |
Sorry I misunderstood your reply :( |
This change is from Kyome22#97, which hopefully fixes Kyome22#96 and Kyome22#73
Fix: #96 #73 #44
set
IncludeNativeLibrariesForSelfExtract
to really publish a singe file without DLLs:ref: https://github.com/dotnet/designs/blob/main/accepted/2020/single-file/design.md#user-experience
To publish single file executable without DLLs, we have to set
IncludeNativeLibrariesForSelfExtract
to true inRunCat.csproj
PublishWithDotNetProdile.pubxml
, otherwise we'll publish executable along with several DLLs:This is why some users (me included) can't run v1.10 and v1.11: lack of some DLLs like
clrcompression.dll
Detailed explanation can be found at this issue: #96