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

Dean Brettle dean@brettle.com
Thu, 17 Mar 2005 09:34:51 -0500


On Wed, 2005-03-16 at 13:19 -0800, Todd Berman wrote:
> On Wed, 2005-03-16 at 09:57 -0500, Dean Brettle wrote:
> <snip>
> 
> >  
> > > > 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.
<snip>
> 
> 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.

OK.  FYI, mono-2.0 support is no longer critical to me (thanks to
Francisco's patch), so I don't plan to implement any of this anytime
soon.

> 
> <snip>
> > 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
> numbers?
> 
> (1.1 and 2.0) ?

Yeah.

--Dean