Hello Mono team,
As you know, Microsoft .NET 4.0 cannot marshal generic delegates. This is a
problem because .NET 4 is the last version of .NET that works on Windows XP
which is still widely used (please, I don't want to argue about this - it's
a fact). On the other hand, I remember having seen
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 -
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
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
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
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
