Re: [Mono-dev] List of cleanup candidates for Mono 4.0
Hi, guys! Sorry for late response. I agree to remove Npgsql from mono and use the nuget packages. This approach is more streamlined with the idea of modularity of the packages. The user should only have Npgsql.dll in her system if she really is going to use it. P.S.: I'd like to use this opportunity to say thank you very much for all those years integrating Npgsql code to Mono codebase. Thank you! On Thu, Nov 27, 2014 at 5:15 PM, Oskar Berggren oskar.bergg...@gmail.com wrote: Can we please finally remove Npgsql? It's been reported: https://bugzilla.novell.com/show_bug.cgi?id=650180 https://bugzilla.xamarin.com/show_bug.cgi?id=23119 The Npgsql included in mono is EXTREMELY ancient and from what I gather useless for most purposes. As far as I can tell, the version included in mono is Ngpsql 1.x, however due to mono versioning the Npgsql assembly will be versioned as 2.x (when I reported it some years ago, maybe it's even 3.x or 4.x now). So mono basically lies about what Npgsql version it is, which adds enormously to the confusion. There is a bunch of open bugs in this old version: https://bugzilla.novell.com/buglist.cgi?quicksearch=npgsql /Oskar 2014-11-27 17:01 GMT+01:00 Alexander Köplinger alex.koeplin...@outlook.com: Judging from the recent version bump in git to 3.99 it looks like the next release after 3.12 will be Mono 4.0. As this is a major release it'll allow us to remove some cruft that is no longer needed, so I thought I'd start a list of things I'd like to see removed: * net2.0/4.0 profiles - this is already in progress * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them * EntityFramework - apart from the fact that we ship a horribly outdated version right now, I see no reason to include this hefty 5+MB DLL in Mono given that EF is open-source and available on NuGet * aspnetwebstack (i.e. MVC+WebApi) - same reasons as for EF, open-source and on NuGet, should be used from there * Rx - I'm not really familiar with this one, but I think it's also on NuGet+open source I'd love to hear your comments/thoughts on this :) -- Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Regards, Francisco Figueiredo Jr. Npgsql Lead Developer http://www.npgsql.org http://gplus.to/franciscojunior http://fxjr.blogspot.com http://twitter.com/franciscojunior ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
Hello, On 2014年11月28日 02:19, Alexander Köplinger wrote: Hey, * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them I like to keep them, to avoid breaking third party build scripts. Good point, however aren't they gonna break anyway when they rely on 2.0 SDK which is no longer there anymore? Maybe now is the time to make people aware they should update the scripts :) * 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. * Rx - I'm not really familiar with this one, but I think it's also on NuGet+open source This one I know contains patches that make it work on Mono. Without these, they wont work. So this might have to wait. Interesting. I had a look at the NuGet package and it ships a portable-net45 version, I always thought this was compatible with Mono? If not, we could maybe look at upstreaming the patches. Basically I agree that we could remove Rx. Yet some works need to be done. Rx imports can be taken in two different parts: desktop and mobile. For desktop, there is no difference (or almost no difference) in the sources. There could be some not-implemented paths in the dependencies, but IIRC I didn't #ifdef-ed out anything for that. For mobiles there are many changes to build and run. - Rx solution/project structure is quite complicated (most likely manually edited) to share several MSBuild targets fragments, as well as using some features that we don't (or maybe didn't) support. So we generate different project files for mobiles, from within mcs/class. (The same xbuild problem applies to desktop, but within mono we build from dll.sources and our own Makefiles just like other assemblies. And for NuGet packages we wouldn't worry about that anyways.) - We use NUnit for tests. Fortunately Rx tests use MSTest which were mostly compatible with NUnit syntax, we reuse that. Yet we needed several changes to the sources (e.g. using NUnit.Framework;). - And the changes are not committed but rather patched at build time (mcs/class/* has some C# script for that). - To make it build, we had to disable some parts by adding #if-s for iOS and Android, which are only for Xamarin. - I'm actually quite unsure how much of the existing Observables work fine on iOS (due to AOT limitation). For Android it worked almost perfectly. The resulting diffs were already too much at that state, so I didn't send them back to the original project. (For example, new tests could easily miss #if MONO use NUnit.Framework; and it won't just build.) Some changes would make sense to send back. IIRC there were some code paths that depend on WinRT or WPF that always exist on MS platforms but not on mono, and I #ifdef-ed out. All those changes are in rx-oss-v2.2 branch in mono/rx so that anyone can review. Anyways, basically we need patched version for mobiles. And some of those reside in mono tree, so before nuking them out they have to be rewritten to become independent of mono tree. Atsushi Eno -- Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
Let's remove my Commons.Xml.Relaxng. It is really isolated work. Atsushi Eno On 2014年11月28日 00:01, Alexander Köplinger wrote: Judging from the recent version bump in git to 3.99 it looks like the next release after 3.12 will be Mono 4.0. As this is a major release it'll allow us to remove some cruft that is no longer needed, so I thought I'd start a list of things I'd like to see removed: * net2.0/4.0 profiles - this is already in progress * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them * EntityFramework - apart from the fact that we ship a horribly outdated version right now, I see no reason to include this hefty 5+MB DLL in Mono given that EF is open-source and available on NuGet * aspnetwebstack (i.e. MVC+WebApi) - same reasons as for EF, open-source and on NuGet, should be used from there * Rx - I'm not really familiar with this one, but I think it's also on NuGet+open source I'd love to hear your comments/thoughts on this :) -- Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
Before we go down this path. Mono 4.0 is not about a general call to clean things up. We are only cleaning up removing the must-haves. Please do not turn this into a threat to clean this up. That can be done independently and on its own schedule. Atsushi, I'll follow up later today on relaxng On Wednesday, December 10, 2014, Atsushi Eno atsushi...@veritas-vos-liberabit.com wrote: Let's remove my Commons.Xml.Relaxng. It is really isolated work. Atsushi Eno On 2014年11月28日 00:01, Alexander Köplinger wrote: Judging from the recent version bump in git to 3.99 it looks like the next release after 3.12 will be Mono 4.0. As this is a major release it'll allow us to remove some cruft that is no longer needed, so I thought I'd start a list of things I'd like to see removed: * net2.0/4.0 profiles - this is already in progress * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them * EntityFramework - apart from the fact that we ship a horribly outdated version right now, I see no reason to include this hefty 5+MB DLL in Mono given that EF is open-source and available on NuGet * aspnetwebstack (i.e. MVC+WebApi) - same reasons as for EF, open-source and on NuGet, should be used from there * Rx - I'm not really familiar with this one, but I think it's also on NuGet+open source I'd love to hear your comments/thoughts on this :) -- Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
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 monofo...@my2cents.co.uk wrote: On 27 November 2014 at 18:19, Alexander Köplinger alex.koeplin...@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@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
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 + From: monodanm...@yahoo.com To: monofo...@my2cents.co.uk; alex.koeplin...@outlook.com CC: mono-devel-list@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 monofo...@my2cents.co.uk wrote: On 27 November 2014 at 18:19, Alexander Köplinger alex.koeplin...@outlook.com wrote: * aspnetwebstack (i.e. MVC+WebApi) - same reasons as for EF, open-source and on NuGet, should be used from thereI 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 listMono-devel-list@lists.ximian.comhttp://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
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.koeplin...@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 + From: monodanm...@yahoo.com To: monofo...@my2cents.co.uk; alex.koeplin...@outlook.com CC: mono-devel-list@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 monofo...@my2cents.co.uk wrote: On 27 November 2014 at 18:19, Alexander Köplinger alex.koeplin...@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@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
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: mig...@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.koeplin...@outlook.com CC: monodanm...@yahoo.com; mono-devel-list@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.koeplin...@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 + From: monodanm...@yahoo.com To: monofo...@my2cents.co.uk; alex.koeplin...@outlook.com CC: mono-devel-list@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 monofo...@my2cents.co.uk wrote: On 27 November 2014 at 18:19, Alexander Köplinger alex.koeplin...@outlook.com wrote: * aspnetwebstack (i.e. MVC+WebApi) - same reasons as for EF, open-source and on NuGet, should be used from thereI 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 listMono-devel-list@lists.ximian.comhttp://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
Ah that one I agree can go away. On Nov 29, 2014 12:17 PM, Alexander Köplinger alex.koeplin...@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: mig...@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.koeplin...@outlook.com CC: monodanm...@yahoo.com; mono-devel-list@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.koeplin...@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 + From: monodanm...@yahoo.com To: monofo...@my2cents.co.uk; alex.koeplin...@outlook.com CC: mono-devel-list@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 monofo...@my2cents.co.uk wrote: On 27 November 2014 at 18:19, Alexander Köplinger alex.koeplin...@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@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] List of cleanup candidates for Mono 4.0
Judging from the recent version bump in git to 3.99 it looks like the next release after 3.12 will be Mono 4.0. As this is a major release it'll allow us to remove some cruft that is no longer needed, so I thought I'd start a list of things I'd like to see removed: * net2.0/4.0 profiles - this is already in progress * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them * EntityFramework - apart from the fact that we ship a horribly outdated version right now, I see no reason to include this hefty 5+MB DLL in Mono given that EF is open-source and available on NuGet * aspnetwebstack (i.e. MVC+WebApi) - same reasons as for EF, open-source and on NuGet, should be used from there * Rx - I'm not really familiar with this one, but I think it's also on NuGet+open source I'd love to hear your comments/thoughts on this :) -- Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
Hey Alex, * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them I like to keep them, to avoid breaking third party build scripts. The removal of frameworks requires that the upstream packages actually work on Mono, and I do not know if this is the case. That said: * EntityFramework - apart from the fact that we ship a horribly outdated version right now, I see no reason to include this hefty 5+MB DLL in Mono given that EF is open-source and available on NuGet I think this one can go, there is an active set of users using it on Unix from NuGet. * 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? * Rx - I'm not really familiar with this one, but I think it's also on NuGet+open source This one I know contains patches that make it work on Mono. Without these, they wont work. So this might have to wait. Miguel ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
Hey, * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them I like to keep them, to avoid breaking third party build scripts. Good point, however aren't they gonna break anyway when they rely on 2.0 SDK which is no longer there anymore? Maybe now is the time to make people aware they should update the scripts :) * 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. * Rx - I'm not really familiar with this one, but I think it's also on NuGet+open source This one I know contains patches that make it work on Mono. Without these, they wont work. So this might have to wait. Interesting. I had a look at the NuGet package and it ships a portable-net45 version, I always thought this was compatible with Mono? If not, we could maybe look at upstreaming the patches. -- Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
On 27.11.2014 19:19, Alexander Köplinger wrote: Hey, * gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles it doesn't make sense to still have them It doesn't make sense to us, but removing them would just break thinks downstream. It's really annoying when such changes are done just for the sake of OCD, so please stop this. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] List of cleanup candidates for Mono 4.0
On 27 November 2014 at 18:19, Alexander Köplinger alex.koeplin...@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@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
