[Mono-dev] Unit Testing process: Community Contributions

Miguel de Icaza miguel at xamarin.com
Tue Oct 21 14:37:04 UTC 2014

> And that's impossible without some level of time-investment in engagement
> - such as having somebody respond to bug reports even if this is to say
> "sorry this is unmaintained - your problem"

Seems like you just volunteered to do this for all the bugs that come in
for Windows.Forms :-)

If only life was that simple :) To reiterate though, I'd have tried to fix
> this if I knew where to begin looking, as I have applications here that
> need System.Windows.Forms and which I can't simply abandon or rewrite.

Time to hire a System.Windows.Forms hacker :-)

Presumably Microsoft still views as System.Windows.Forms as maintained? Or
> have they abandoned it too?

You will have to ask them.

Windows.Forms is a wrapper around the Win32 UI API.   So for them, the
maintenance means "keep the wrapper working for our underlying API".   Mono
had to reimplement everything from the ground up, and simulate many pieces
of Win32.   So it is a much more complex problem for Mono than it is for

Is there a place where I can see a matrix of what components the Mono
> project views as unmaintained and therefore what kind of .NET applications
> may no longer run under the current release of Mono?

There are a few on the web site, but they are likely not up to date.

You can submit pull request for updating the web site.

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

More information about the Mono-devel-list mailing list