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

Todd Berman
Wed, 16 Mar 2005 13:19:10 -0800

On Wed, 2005-03-16 at 09:57 -0500, Dean Brettle wrote:

> > > 1. changing .prjx schema to remove version info for GAC refs and add
> > > per-configuration attrs controlling mono-1.0 vs mono-2.0.
> > 
> > This isnt needed at all, or acceptable. You should (via the GUI) allow
> > one or the other, and for MONO-SYSTEM dlls, when the project option
> > changes, you change the references.
> Sorry, I wasn't clear.  I meant a *per-configuration* project option.
> The idea would be that you could have a Debug-Mono-1.0 config and a
> Debug-Mono-2.0 config.  The references (and more importantly their
> versions) are currently specified project-wide, so I think the .prjx
> format would need to change to handle that.
> Thoughts?

Doesn't seem useful to me. It should be per project. At least, lets get
that working, and then in the future, if it comes up, we can deal with
separate configuration options.

> Agreed.  I was thinking a "targetRuntime" enum.  Initial valid values
> would be "mono-1.0" and "mono-2.0".  Sound right?

Yes, however would it make more sense to use the .net versioning

(1.1 and 2.0) ?

> > > 
> > > Also, I'd appreciate any info on differences beteen gmcs usage and mcs
> > > usage?  "gmcs --help" and "mcs --help" produce almost identical results.
> > > 
> > 
> > There are none (that I know of)
> FYI, I tried using gmcs and, IMO, it is still too unstable for
> widespread use.  I ran into a number of bugs that were specific to gmcs.
> How confident are you that it is wrong to compile with mcs when
> targeting mono-2.0?  Who would know for sure?

120% confident.