tags:

views:

192

answers:

3

Does Mono miss any functionality from .NET? If not, when will we see official MS recognition for it, like including Mono platforms in the Platforms section on MSDN?

It seems like they are seen as separate things.

+6  A: 

They are separate things - Mono is a competitor to .NET. I doubt very much that we'll ever see it being advertised on MSDN. Would you expect Microsoft to have an advert for a Linux distribution there? ;)

(And no, Mono doesn't contain everything from .NET.)

Jon Skeet
More specifically Mono is a Novell product. http://www.mono-project.com/Main_Page
EBGreen
Gah! Fie on you Jon Skeet and your god-like typing/linking abilities. I can't get any answers in today!!!! 8^D
Dillie-O
They do however correct a few bugs that .Net hasn't fixed yet. :)
EBGreen
This FAQ page also has a nice overview of what Mono does and does not contain: http://www.mono-project.com/FAQ:_General
Dillie-O
Would ASP.NET MVC work on MONO?
IceHeat
Thanks Jon. I didn't know that. If Mono is a competitor, then who's gonna take care of the claimed platform-independence of .NET?
Joan Venge
@Joan: What claimed platform independence is that? It's (largely) processor independent, but I don't think MS claims that it's platform independent. The CLI spec is (largely), but that's not the same thing... It's certainly not the same kind of selling point for .NET that it is for Java.
Jon Skeet
@Jon: Thanks, I see what you mean. I thought it was also advertised as platform independent in addition to processor independent. :)
Joan Venge
@Iceheat: it works, but it's against the license terms at the moment. See: http://stackoverflow.com/questions/202430/
Joel Coehoorn
If you're interested in mono, you may also want to follow this user: http://stackoverflow.com/users/16929/miguel-de-icaza
Joel Coehoorn
I didn't know he was registered here. It's awesome!
Joan Venge
You can also hear Miguel discussing this among other Mono topics on the Herding Code podcast (episodes 28 and 29): http://herdingcode.com/
EBGreen
+3  A: 

To see the status of anything in the Mono object model vs the .NET Framework you can go to this page...

Jason Punyon
Any reason for the DV?
Jason Punyon
I think someone is pushing an agenda. Jon's answer got at least 2 DVs and it is completely correct.
EBGreen
@Joan Venge: Down Vote
Jason Punyon
Thanks JPunyon. How do you see it's got 2 DV?
Joan Venge
I know that it got 2 DV because of watching the vote changes. It is true that the pattern I saw could have been 1 DV and one detracted UV, but I suspect 2 DV is more likely.
EBGreen
Thanks EBGreen, I thought there is a place that shows the progress of votes, like the replies history.
Joan Venge
After the bot runs behind the scenes it would be possible to go to the rep tab on Jon's profile and see how many UVs/DVs the answer got.
EBGreen
@EBGreen - Actually...you would be able to do that...but he's already maxed out for today...so all you see is the 15 for acceptance...
Jason Punyon
Aah...good point.
EBGreen
+2  A: 

MoMA is a useful tool for examining your assemblies and reporting on any potential issues (e.g., not implemented methods).

There are a couple of things to be aware of with Mono. Despite a good report from MoMA, we've run into bugs (including regressions in the new 2.2 release) as you would expect. You do have the source and I really recommend being able to build Mono (in particular the managed part which compiles the libraries). Be sure to push bug reports via the public bugzilla for Mono.

Also, be aware of dependencies on third party libraries. Thorough testing is a must. For example, we tried using xUnit.net with mono and it mostly worked well. However, it uses an ugly reflection hack to set the value of a private member variable (in the Exception class). Of course, something like this is bound to cause runtime issues. Once again, source code to the rescue as xUnit.net is OpenSource.

dpp