[Mono-dev] Killing .NET 2.0 support?

[Miguel de Icaza]

>
> 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.

Miguel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140519/c01002d7/attachment.html>