El dl 18 de 05 de 2009 a les 21:13 -0400, en/na Miguel de Icaza va
escriure:
I could see Mono.Addins going either way. It probably is used by enough
Gtk# apps to justify it being in the Gtk# installer.
My only concern with Mono.Addins is that once we ship it, it is
effectively set in
From: Mike Kestner
Feedback appreciated. In particular I'd like to hear from those of
you
using the current Gtk# for .net installer or those considering win32
ports in the future. Which would you prefer, one installer or two?
If
one, should it remain the Gtk# for .net installer for
I am currently working to provide some additional installation
capabilities to support the porting of MD to windows. This includes
shipping libraries like Mono.Posix, Mono.GetOptions, SharpZipLib, and
Mono.Addins.
We've previously received requests to include Mono.Posix in the Gtk#
for .net
I am definitely against having a separate installer for these libraries,
so I like the way you are thinking. :)
Some of these make sense to put with the Gtk# installer, like Mono.Posix.
Generally on Windows, you ship your dependencies with your application.
I would say something like
I could see Mono.Addins going either way. It probably is used by enough
Gtk# apps to justify it being in the Gtk# installer.
My only concern with Mono.Addins is that once we ship it, it is
effectively set in stone (or we have to incrementally add new versions
of it, one for each API
The latest Windows installer doesn't set any environment variables in
the wrapper scripts and batch files (MONO_PATH, etc...). This works
fine in finding the gac binaries.
I've looked into doing this for the linux installer as well, and some
programs didn't work. gmcs worked, but mcs didn't
Wade,
The latest Windows installer doesn't set any environment variables in
the wrapper scripts and batch files (MONO_PATH, etc...). This works
fine in finding the gac binaries.
The path to the mono assemblies is computed from
the executable's file name of the process that loads
mono.dll.
Hello,
The latest Windows installer doesn't set any environment variables in
the wrapper scripts and batch files (MONO_PATH, etc...). This works
fine in finding the gac binaries.
I've looked into doing this for the linux installer as well, and some
programs didn't work. gmcs worked, but
