I create an RPM of the runtime the quick and dirty way, with FPM, and then it is installed into a path of my choosing, basically as a private runtime for my application:
http://loosexaml.wordpress.com/2013/07/27/creating-a-mono-3-rpm-on-centos/ You could do basically the same to package up an RPM that contains the mono runtime as well as your application. If you're using something other than RPM, well, the FPM module supports many different formats. Keep in mind you may need to deviate from those instructions if you have other dependencies. The other option is to use AOT compilation, but keep in mind that means you are statically linking to the runtime and that triggers some LGPL license requirements as stated here: http://www.mono-project.com/Mono:Runtime On Aug 3, 2013, at 10:46 AM, Ravior <tom_ri...@venion.net> wrote: > Hello, > > I would like to either deploy Mono DLL's my application uses with it, so > that the mono framework does not to be installed at all or I would like a > silent installer for the mono framework. > > Its just about not bugging the user at all about stuff like that. > > What would be best to do and how? > > Greetings, > > Ravior > > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/Deploying-Mono-tp4660389.html > Sent from the Mono - General mailing list archive at Nabble.com. > _______________________________________________ > Mono-list maillist - Mono-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
