It is there since .NET 1.0, see NGEN.
However it is done at installation time with dynamic linking only.
And Mono has had it since ages, used by Unity and Xamarin.
This is the porting of UWP .NET Native to mainline .NET.
However it is done at installation time with dynamic linking only.
And Mono has had it since ages, used by Unity and Xamarin.
This is the porting of UWP .NET Native to mainline .NET.
go build
and you get 1 portable tiny executablengen, .net native, mono etc, you need more steps, and you get a folder with a bunch of files and folders
that's why these solutions didn't took off
go build
and you get 1 portable tiny executable, provided it is 100% Go code, without any dependency on cgo or OS APIs not packaged into the Go runtime.These solutions did take off, how do you think Unity games for PS, Xbox, Wii, Switch, Windows 10 UWP, and Xamarin apps for iOS/Android get delivered?
dotnet publish -p:PublishSingleFile=trueAnd check the small print on your platform as to whether it's really single file not requiring any other dependencies alongside it.
This no longer happens since .net 5.