Mono has an implementation of ASP.NET, ASP.NET MVC and ASP.NET AJAX.
- ASP.NET FAQ for common questions on ASP.NET.
- Hosting on Apache servers.
- Hosting with FastCGI-based servers.
- Hosting with CGI-based servers.
- Hosting with Nginx.
- Porting ASP.NET applications.
Mono’s ASP.NET implementations supports two kinds of applications:
- Web Forms (Web Applications infrastructure).
- Web Services (the SOAP-based RPC system).
Status and tests for ASP.NET 2.0 are available in our ASPTests page.
Running ASP.NET applications
To run your ASP.NET applications with Mono, you have three classes of options:
- Apache hosting: use mod_mono, a module that allows Apache to serve ASP.NET applications.
- FastCGI hosting: use the FastCGI hosting if you have a web server that supports the FastCGI protocol (for example Nginx) for extending the server. You also may use a web server that only has support for CGI using cgi-fcgi.
- XSP: this is a simple way to get started, a lightweight and simple webserver written in C#.
For deploying applications, we recommend the use of the mod_mono or FastCGI approaches, as that will give you all the configuration options and flexibility that come with using Apache or a FastCGI server.
For quickly getting started, get familiar with Mono and ASP.NET, XSP is the ideal solution. Keep in mind that XSP is a very limited server and is only useful to get acquainted with ASP.NET and Mono, it only support HTTP 1.0 and does not provide much extensibility or configuration.
More advanced users can use the HttpListener and the ASP.NET hosting to create their own hosts for ASP.NET applications.
ASP.NET hosting with Apache
The mod_mono module runs within an Apache process and passes all the requests to ASP.NET applications to an external Mono process that actually hosts your ASP.NET applications. The external ASP.NET host is called “mod-mono-server” and is part of the XSP module.
To use this, you must download and install the mod_mono and xsp components of Mono. mod_mono contains the actual Apache module, and xsp contains the actual ASP.NET hosting engine, both are available from our download page.
See the mod_mono page for details on installation and configuration.
ASP.NET hosting with Nginx
Nginx is a high-performance HTTP server which support running ASP.NET and ASP.NET MVC web applications through FastCGI protocol. See the FastCGI Nginx page for details on installation and configuration.
ASP.NET hosting with XSP
XSP is a standalone web server written in C# that can be used to run your ASP.NET applications with minimal effort. XSP works under both the Mono and Microsoft runtimes. The code is available from our download page (look for XSP web server) or from the git repository (module name: xsp).
The easiest way to start XSP is to run it from within the root directory of your application. It will serve requests on port 8080. Place additional assemblies in the bin directory. Other XSP options can be set on the command line, such as the application directory and the port to listen on.
XSP comes with a set of pages, controls and web services that you can use to test the server and see what ASP.NET looks like.
For example, once you install XSP, you can try some samples like this:
$ cd /usr/lib/xsp/test $ xsp Listening on port: 8080 Listening on address: 0.0.0.0 Root directory: /home/cvs/mcs/class/corlib/Microsoft.Win32 Hit Return to stop the server.
You can now browse to http://localhost:8080 and see various sample programs
Additionally, you can configure Mono-specific ASP.NET settings (to have applications that behave differently depending on the operating system they are deployed in) using the ASP.NET Settings Mapping engine.
Check out ASP.NET Modules for details on how to support deflate/gzip encodings and authentication.
By default xsp and xsp2 run in Release mode, which means that debugging line-number information will not be available in stack traces when errors occur.
To obtain line numbers in stack traces you need to do two things:
- Enable Debug code generation in your page. 2. Run Mono with the –debug command line option.
You must enable debug code generation in your page using the Debug=”true” in the top of your page, or setting the compilation flag in Web.config (compilation option).
Use the –debug command line option to Mono, this is done by setting the MONO_OPTIONS environment variable, like this:
$ MONO_OPTIONS=--debug xsp2 Listening on port: 8080 (non-secure) Listening on address: 0.0.0.0 Root directory: /tmp/us Hit Return to stop the server.
To do the same with the Apache mod_mono module, use the MonoDebug true directive in your apache configuration file.
Mono supports ASP.NET 2.0, ASP.NET AJAX and a handful of 3.5 controls.
Mono’s ASP.NET does not implement the following features:
- Precompiled updatable web sites.
- WebParts APIs.
Work in Progress
Users interested in the latest version of mod_mono and xsp can retrieve these from our public git repository. The module names are mod_mono and xsp respectively. You will also need to check out the mcs module as the System.Web classes are in mcs/class/System.Web.