Closed ghost closed 5 years ago
i think you can add /p:PublishSingleFile=true after dotnet command like :dotnet publish -c release -r linux-x64 /p:PublishSingleFile=true
, Instead of using dotnet-warp at .net core 3.0
Yep, .NET Core 3.0 has this mechanism built in. So it would be: dotnet publish -c Release -r linux-x64 /p:PublishSingleFile=true /p:PublishTrimmed=true
Running external ILLink.Tasks on .NET Core 3.0 is not supported
Note: In previous versions of .NET Core, ILLink.Tasks was shipped as an external NuGet package and provided much of the same functionality. It is no longer supported – please update to the .NET Core 3.0 SDK and try the new experience!
Source: https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0/
Yes but according to scott hanselman, this tool can get to 9 MB binaries but the dotnet core 3.0 trimmer only gets me to 30 MB.
So dotnet-warp is way better, you should make it work with dotnet core 3.0
ILLink.Tasks package, which dotnet-warp uses to pack, is not working on .NET Core 3.0. There is nothing I can do to make it work, as it was obsoleted for a reason - there is already built in mechanism for that. Sadly, ILLink.Tasks package was more configurable, and more aggresive trimming was possible. You could try approach given here: https://www.hanselman.com/blog/MakingATinyNETCore30EntirelySelfcontainedSingleExecutable.aspx
Thanks!
the output exe/dll from a normal publish works, however.