5 ms·
> There's something nice about the ergonomics of a single file compared to a single folder though Agreed. We are going to move to proper single file (or as clo
by bob1029 5y ago
> There's something nice about the ergonomics of a single file compared to a single folder though
Agreed. We are going to move to proper single file (or as close as we can get) as soon as any sort of meaningful AOT compilation is available:
https://github.com/dotnet/runtimelab/tree/feature/NativeAOT https://github.com/dotnet/runtimelab/tree/feature/NativeAOT
https://github.com/dotnet/runtimelab/issues/248 https://github.com/dotnet/runtimelab/issues/248
There is a "PublishSingleFile" option, but that is just a zip file in disguise.
- ripley12 5y ago> There is a "PublishSingleFile" option, but that is just a zip file in disguise. I don't quite agree. These days (as of .NET 5), if you publish a single-file app all .NET libraries live in the executable and do not need to be unpacked at runtime. Native libraries still need to get unpacked at runtime (if your application uses any; many don't) but I haven't found that to be a big deal in practice.
- bob1029 5y ago> and do not need to be unpacked at runtime Thanks for the correction/clarification. I had not realized this was a thing now. Will give this option another look.