[Mono-dev] Heads up: Elimination of the 2.0 and 4.0 profiles
marek.safar at gmail.com
Sat Oct 25 08:01:19 UTC 2014
I'll try to reformulate my question. Do I understand correctly that in
> new version of mono it will not be possible to compile assembly for
> Mono/.NET 3.5 target and use the compiled assembly in Unity 3D (because
> of referencing different corlib libraries in Unity (corlib 2.0) and
> compiled assembly (if corlib 2.0 is removed))?
That's correct. You cannot compile code using (targeting) 4.x profile and
run it using 2.0 mscorlib. Due to simple reason that 4.x introduces new
apis which are not available in 2.0. Good example is Monitor.Enter (object,
ref bool) method.
> On Fri, 2014-10-24 at 12:22 -0400, Miguel de Icaza wrote:
> > Hey,
> > There is no 3.5 profile. There are currently only 2.0, 4.0
> > (reference assemblies), 4.5 and the mobile versions (mobile, android,
> > ios).
> > What you think is 3.5 are assemblies introduced at 3.5, but we ship
> > with the above 4.0/4.5 ones.
> > On Fri, Oct 24, 2014 at 12:33 AM, xplicit <svg at ngs.ru> wrote:
> > Miguel de Icaza-6 wrote
> > > We are going to remove the build for the .NET 2.0 APIs from
> > Mono which are
> > > currently provided for bug/feature-compatibility for .NET
> > 2.0
> > > applications.
> > Will you save .NET 3.5 or you are going to remove corlib 2.0
> > at all?
> > Removing 2.0 profile is a good thing, but without support
> > of .NET 3.5 it
> > would be difficult to work with Unity 3D at least.
> > --
> > View this message in context:
> > Sent from the Mono - Dev mailing list archive at Nabble.com.
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list