[Mono-dev] Killing .NET 2.0 support?
stapostol at gmail.com
Wed May 21 13:19:28 UTC 2014
4.0 is 4 years old by now, so this makes sense.
You might wish to make a heads up announcement to give distros some time to
adapt (in the unlikely case some might wish to implement some sort of
side-by-side installation for compatibility.) The Wine project may also be
affected, since they are now shipping Mono/Windows.
Personally, I've been looking for a good reason to move OpenTK to .Net 4.0
- this one is just about perfect.
2014-05-19 20:59 GMT+02:00 Miguel de Icaza <miguel at xamarin.com>:
> I don't know whether it's relevant, however we recently upgraded an
>> ASP.NET WebForms application from 2.0 to 4.0 and there were numerous
>> little gotchas on the. NET runtime. Granted a lot of these were with third
>> party libraries, but I would be concerned that this could simply cause some
>> applications to just not work. Therefore causing people to need to setup
>> parallel mom installations.
>> That said, I don't know anything about the approach you're suggesting as
>> to whether the same issues could occur.
> They could happen, there is nothing on my approach that would magically
> fix it.
> But we have limited bandwidth, and we are struggling to maintain pre-async
> code in the class libraries.
> The lack of await turns every programmer into a glorified accountant,
> bookeeping things everywhere. And we have a series of bugs that we have
> struggled for months to solve due to what amounts to poor bookkeeping in
> our part.
> So we can either try to suck it up and fix the bookkeeping --in a piece of
> code that is basically impenetrable-- or accelerate our pace of development
> by killing the old stack.
> 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