4 ms·
Maybe releasing a container with .net core included and using that to bootstrap on other platforms could work? You would run the container with the source code
by Scaevolus 10y ago
Maybe releasing a container with .net core included and using that to bootstrap on other platforms could work? You would run the container with the source code and build directories from the host mounted and run the appropriate command.
It's not perfect, since now you have a dependency on Docker (or equivalent), but maybe it's still an improvement?
There's also some efforts like [snap](http://snapcraft.io/ http://snapcraft.io/) to make it easier to release binaries with all their dependencies packaged together, but I expect making it work for a complex project like .NET is difficult.
- loeg 10y agoWe call them "statically linked binaries". Yeah, that would work well for bootstrapping.
- Scaevolus 10y agoStatically linking binaries doesn't help when there's a bunch of auxiliary resources (bytecode/class libraries) that the compiler needs to run. You can bake that into one binary in additional segments, but it can be fiddly and require more extensive code changes to make various fopen() calls read from the binary instead of a standalone file.
- loeg 10y agoFortunately, this is not the problem described above.