[Mono-dev] Killing .NET 2.0 support?
monoforum at my2cents.co.uk
Wed May 14 21:57:35 UTC 2014
I don't know whether it's relevant, however we recently upgraded an
ASP.NETWebForms application from 2.0 to 4.0 and there were numerous
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.
My2cents would be that compatibility issues would need to be fast tracked
if you did that.
Personally, I only use 4.0 and above now, so for me, do as you will.
Anything to give people time to focus on the important, useful things in
the framework (like making MVC5 and OWIN security work)
On 14 May 2014 19:47, "Rafael Teixeira" <monoman at gmail.com> wrote:
> I think it is a good move. But all tests for NET_20 profile (as compiled
> in that profile) must be run and succeed in the NET_45 profile, before
> killing it.
> My 2 cents,
> Rafael Teixeira
> On Wed, May 14, 2014 at 3:32 PM, Miguel de Icaza <miguel at xamarin.com>wrote:
>> Hey guys,
>> Maintaining the .NET API has become a pain and we feel that everything
>> that could run with 2.0 could run with 4.5.
>> So we are wondering if we should just kill this and get on with our lives.
>> It would let us use Async internally in our class libraries (among other
>> I wonder if we could just patch the Mono C runtime to redirect all
>> references to the 2.0 assemblies at runtime to the 4.0 gac?
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> 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