Geek Answers Handbook

Are there any real limitations in Mono regarding ASP.NET?

Iā€™m a junior developer. I studied at college last year. I am mainly focused on asp.net and even have part-time programming in this language. I'm interested in converting to linux, and since visual studio is not supported, write my code in Mono.

Are there any noticeable limitations in Mono that I should be aware of (regarding ASP.NET)?

+6
linux mono
source share
4 answers

I would say that the biggest thing you lose is IIS. ASP.net and IIS were very closely related. Many of the benefits of ASP.net come from hosting features in IIS. The biggest I can name is the ability of HTTP.sys to respond directly to a request in kernel mode if the page is in cache. This means that an open socket responds immediately and can be an order of magnitude greater than the number of requests to your web server.

+6
source share

According to the Mono website:

Mono ASP.Net does not implement the following functions:

  • Precompiled Websites
  • Web page API.

Also, most if not all third-party ASP.Net controls are not compatible with Mono, unless otherwise specified. ComponentArt elements, for example, cannot be used in Mono. However, there is no reason to believe that this will not change, since Mono is gaining popularity. ComponentArts already mentioned that they are considering adding support in the future.

+7
source share

A bit about the edge, but Microsoft Web Services Enhancements is not supported in Mono. I ran into this problem trying to get some WSE services to work with Mono.

+2
source share

With regard to web services, there are two very good open source alternatives: ServiceStack.Net (using it) and NANCY .

These areas are much easier to implement, use and maintain IMHO than services built on top of WCF.

+1
source share

More articles:


All Articles