Mono framework completeness?

[Mark R]

I've been trying to port a tool from Windows to Mac, and as it's written in pure .Net 2.0, I thought this wouldn't be too difficult.

I'm using Mono 2.10.8 on Mac OS Mountain Lion.

The problem is that every time I think I've got things working during my functionality testing, I end up hitting a NotImplementedException or a type initializer exception (admitted in fairly obscure parts of Sockets/async IO) but nevertheless, these are paths that I would expect to be reasonably well trodden.

I'm pretty sure I've managed to work around them all, but I was wondering if there was a list of missing interfaces.

I'm only using pretty basic stuff - System.* namespaces (none of the Microsoft.* extensions, etc.), and no P/Invoke or similar.

 

[Train]

It's been a while, but last I checked, they had a status list of all the framework classes on the mono site that said which were implemented, not yet, in progress, and not gonna happen.

Could be they were implemented, but never got merged into the main build. Might be worth checking out the source.

 

[Cogman]

Here is the list that Train was reffering to http://go-mono.com/status/

Looks like a fair amount of the sockets stuff is unimplemented.