What kind of thing is Mono not suitable for?

I started my typical web project from scratch using the Mono platform. You know, web services, user interface, MySQL database, all this. I heard on the net that this is not an ideal implementation of the .NET platform, but so far I can’t find anything that’s bad for it. I see that the odd "Not implemented" appear in intellesense, but do not fall into any misses or dead ends.

Did you hit a brick wall with a .Net function that is not implemented in Mono?

+5
source share
2 answers

In my opinion, the guys working on Mono have quite a few features that have completed their version of ASP.NET 2.0. Now I know that they worked to use .NET 3.5, such as LINQ, and such impressions, but I'm not too sure how much they are connected with this. I know that working on the desktop was a bit more complicated, and they worked on getting some of the specific namespaces designed on the desktop like System.Windows.Forms.

Here's an article that dives a little deeper into the entire Mono installation. It is a bit old, but has a lot of code and descriptions for digesting.

Good luck, and I hope that Mono will develop for your project.

+1
source

- , GC - , WPF, WF, Entity Framework, WCF, MonoDevelop Eclipse/VS.Net, mod_mono tomcat/IIS, - , ... , , , . # - , , . .Net , JDK , , , , ; - Java. Java / , Terracotta, Hibernate ( .net), Ehcache, Compass,... , Sun , Java ( ), ,...

, - . , , , . , .

,

+1

All Articles