Hubert Rybak

+1, it would be nice to pass that as additional parameter. Most importantly, version.

I created .NET CLI global tool, which is a wrapper around Warp and ILLink.Tasks for optional assembly stripping before packing, maybe someone would be interested: https://www.nuget.org/packages/dotnet-warp/

The bug you linked is for .NET 4.7.1, and this tool works on .NET Core >2.1. Are you 100% you are running on x64? What is the output of "SET...

There is a check to ensure that you are running x64, because warp only supports x64. There is a check: https://github.com/Hubert-Rybak/dotnet-warp/blob/af7e332c11f46bf68f98d0467f26709473779817/src/dotnet-warp/Platform.cs#L11 So basically, RuntimeInformation.ProcessArchitecture must reporting something different than x64....

Trimming will not work, packing should work. So you can trim with 3.0 and then pack with this tool (like https://www.hanselman.com/blog/MakingATinyNETCore30EntirelySelfcontainedSingleExecutable.aspx). This error looks strange, could you paste output you...

I suspect that this is because of /p:RootAllApplicationAssemblies=false which is set by this tool when running with an "aggressive" flag. This is somewhat risky and could break your app, so...