I had a look at how to deploy a modern ASP.NET thingee the other day and it was super enterprisey. It doesn't produce a single file, it produces a 'publish' folder, and you need something called a "kestrel" server...
Say what you will about node.js but you just run the script and slap caddy or nginx in-front of it.
[0]: https://docs.microsoft.com/en-us/dotnet/core/deploying/singl...
[1]: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/se...
Adding an nginx as a proxy is also simple.
Nothing enterprisey about it. Also, the "Publish" folder is basically the "build" folders you get from other stacks.
Native AOT is on the roadmap for net7 which is good but very minimal support. For instance asp.net mvc is a non-goal (https://github.com/dotnet/runtime/issues/61231), so probably another 3 or 4 years before it's well supported.
Building an app that has the runtime bundled with it (no need to install .Net) or a single file executable is just a matter of setting a few build flags.