[Mono-dev] List of cleanup candidates for Mono 4.0

[Miguel de Icaza]

Ah that one I agree can go away.
On Nov 29, 2014 12:17 PM, "Alexander Köplinger" <alex.koeplinger at outlook.com>
wrote:

> This has nothing to do with .NET Core, in the case of npgsql we only annoy
> people by shipping an ancient version with Mono, like a few people
> pointed out on this thread.
> E.g. a core contributor asking us to remove it from Mono:
> https://bugzilla.xamarin.com/show_bug.cgi?id=23119
>
> -- Alex
>
> ------------------------------
> From: miguel at xamarin.com
> Date: Sat, 29 Nov 2014 12:04:12 -0500
> Subject: Re: [Mono-dev] List of cleanup candidates for Mono 4.0
> To: alex.koeplinger at outlook.com
> CC: monodanmorg at yahoo.com; mono-devel-list at lists.ximian.com
>
> Hey,
>
> We want to implement the same .NET Core interface when it becomes
> available and to support that scenario.
>
> But until that world exists and all the components are cross platform, we
> are just going to be annoying a bunch of people.
>
> On Sat, Nov 29, 2014 at 11:05 AM, Alexander Köplinger <
> alex.koeplinger at outlook.com> wrote:
>
> Yeah, I think having something in-box with Mono just for convenience makes
> less sense these days given that we have NuGet.
> I'd actually advocate removing everything from the Mono distribution that
> does not also ship with the .NET BCL (except maybe things like Mono.Simd
> which requires specific runtime features).
> The world is moving towards a more modular approach and (just like .NET
> Core) we should leverage NuGet where we can.
>
> -- Alex
>
> ------------------------------
> Date: Sat, 29 Nov 2014 15:50:05 +0000
> From: monodanmorg at yahoo.com
> To: monoforum at my2cents.co.uk; alex.koeplinger at outlook.com
> CC: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-dev] List of cleanup candidates for Mono 4.0
>
> I agree with removing Npgsql from Mono.  Or either convince someone to
> commit the latest version of Npgsql to mono.  It would have to build with
> mono's build system though.  Francisco?
>
> The main reason it was included in mono was so you could have an
> out-of-the-box experience with mono connecting to Postgres.
>
>
>   On Thursday, November 27, 2014 6:07 PM, Martin Thwaites <
> monoforum at my2cents.co.uk> wrote:
>
>
>
>
> On 27 November 2014 at 18:19, Alexander Köplinger <
> alex.koeplinger at outlook.com> wrote:
>
>
>
> * aspnetwebstack (i.e. MVC+WebApi) -> same reasons as for EF, open-source
> and on NuGet, should be used from there
>
>
> I am actually not sure about this one, is that really the case?
>
>
> The latest XamarinStudio/MonoDevelop MVC template installs it from NuGet,
> so I think it should be fine to remove. It might not work perfectly until
> the System.Web from referencesource is integrated, but the same applies to
> the existing (outdated) copy we ship currently.
>
>
>
> This is something I've been working on.  MVC 5.2.2 (the one available on
> NuGet) just doesn't work at the moment due to this pull
> https://github.com/mono/mono/pull/1349 being required (and I haven't had
> chance to fix the things that Miguel wanted).
>
> In addition, the old notes on getting MVC 3 working on mono, said to
> remove the MS supplied versions of the dlls IIRC, so these would stop
> working on upgrade (and replacing with the nuget ones for MVC3 probably
> won't work).
>
> _______________________________________________
> 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
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20141129/36055aa3/attachment-0001.html>