Using mono-2.0 [was Re: [MonoDevelop] Import Visual Studio .NET Projects]

Dean Brettle
Tue, 15 Mar 2005 23:36:44 -0500

On Tue, 2005-03-15 at 10:21 -0800, Todd Berman wrote:
> I think to accept
> allowing 2.0 assemblies to be used we have to have the following (all in
> one single patch)
> 1) Ability to pick gmcs/mcs and use it properly
> 2) Only allow gmcs + 2.0 assemblies or mcs + 1.0 assemblies and not
> allow mixing 1.0 and 2.0 assemblies.

OK, makes sense.  As a first pass, would you accept a patch that uses an
env var (say MONODEVELOP_USE_MONO2) to determine whether to use gmcs+2.0
assemblies?  A future patch could replace the env var with some GUI (say
something in Edit->Preferences->MonoDevelop Options->Build?).  

In the long run, perhaps it should be a project configuration option.
However that looks like a considerably larger task.  Looks like it would
1. changing .prjx schema to remove version info for GAC refs and add
per-configuration attrs controlling mono-1.0 vs mono-2.0.
2. removing ref version info from the Edit References GAC tab 
3. changing SystemAssemblyService to provide the correct assemblies
based on the project configuration.
4. adding an option to the project config options to select mono-2.0 vs

Sound about right?

Also, I'd appreciate any info on differences beteen gmcs usage and mcs
usage?  "gmcs --help" and "mcs --help" produce almost identical results.