• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Mono framework completeness?

Mark R

Diamond Member
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.
 
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.
 
Back
Top