/me raises hand!
It's got quite a number of things left.
The report which I've done is here:
http://flowblok.justfree.com/output.html
I've only analysed Vixen, because that's the best starting point.
Oh, and it's Vixen 2.0 beta 2, because I don't have beta 3 on my computer at the moment! The report's probably almost the same, though.
When Mono releases version 2.0, that means that it completely supports Vixen. (Unless KC has to use some .NET 3.0 methods). Because MS develop both the specifications and an implementation, their implementation will always be ahead of Mono.
One main problem is making a Inpout32.dll for Linux / Mac / other. It needs to do the raw parallel operations. Serial is fine, however, because that's provided through the .NET System.IO.Ports namespace;
Also, you need to work out how to provide the fmod library, which Vixen uses for its audio work.
I've asked K.C. for a mono build, and he's said that he'll look at it while travelling.
Tony is right, and here's a simple explanation of it:
Mono is a .Net implementation, .Net is a framework used by CLI programs (like Vixen). Microsoft produce MS .Net, which is their .Net implementation. However, they only do that for Windows.