I wish we had more options but mkbundle seems to be the way to go. We are trying to make the smallest Docker containers we can and drop an executable (statically compiled mono service) into the container. Unfortunately a functional mono runtime installation is much larger, and we would have to create a new runtime install for each version of mono so that services that were created under mono 4.1 don't end up on 4.2 without testing.
-----Original Message----- From: Edward Ned Harvey (mono) [mailto:edward.harvey.m...@clevertrove.com] Sent: Wednesday, March 09, 2016 8:35 AM To: Eugene Kobrinsky <c...@integrate.com>; mono-list@lists.ximian.com Subject: RE: mono-core still required after using mkbundle --static to make executable > From: mono-list-boun...@lists.ximian.com [mailto:mono-list- > boun...@lists.ximian.com] On Behalf Of Eugene Kobrinsky > > We finally got mkbundle --static to build a single executable of our > microservice, but when we move it to another machine, it fails to run > unless we install mono-core (this is all on Cent0S 7 installs). mkbundle works poorly. If you need to use it, please ignore me. The advice is to rely on having a functional mono installation, unless you have a solid reason not to (and hence require mkbundle). _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
