Product docs and API reference are now on Akamai TechDocs.
Search product docs.
Search for “” in product docs.
Search API reference.
Search for “” in API reference.
Search Results
 results matching 
 results
No Results
Filters
Build ASP.NET Applications with mod_mono and Apache on Debian 5
- Deprecated guides:
- Ubuntuu 10.04
- Ubuntu 9.10
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
DeprecatedThis guide has been deprecated and is no longer being maintained.
mod_mono
is an Apache module that makes it possible to run ASP.NET applications in Linux environments running Apache. While ASP.NET is a Microsoft technology and is traditionally used with IIS, mod_mono
has become a viable option for deploying ASP.NET applications on Linux. This guide is inspired by the mod_mono guide created by the Ubuntu Community
and the Mono Project’s Apache and Mono document
with minor modifications. This guide does not cover installation and configuration of the Mono IDE which is used to develop ASP.NET applications on Linux. If you are interested in developing using Visual Studio for Mono, you can download a 30-day trial of the commercial Mono Tools plugin at the Mono Tools for Visual Studio page
.
This guide assumes that you’ve followed the steps outlined in our Setting Up and Securing a Compute Instance
. You will install the Apache web server
with very minimal configuration. If you already have Apache installed and configured, you may omit these steps; however, if you have not installed Apache and are unfamiliar with this server read the installation guide for additional documentation. Additionally, mod_mono
is incompatible with the integrated PHP interpreter described in other guides. If you need to have both mod_mono and PHP running on the same Apache server you will need to run PHP scripts using the CGI method
Set the Hostname
Before you begin installing and configuring the components described in this guide, please make sure you’ve followed our instructions for setting your hostname . Issue the following commands to make sure it is set properly:
hostname
hostname -f
The first command should show your short hostname, and the second should show your fully qualified domain name (FQDN).
Install Required Software
Before beginning the installation process, issue the following command to update your package lists:
apt-get update
apt-get upgrade
Install Apache
If you already have Apache installed and configured, you can safely skip this section of the guide. Install Apache by running the following command:
apt-get install apache2
As mentioned earlier, you will need to go to the installation guide if you wish to configure your server beyond the default configuration.
Install mod_mono
The Apache daemon must be stopped before mod_mono
is installed. Issue the following command to stop the apache process:
/etc/init.d/apache2 stop
At this point we’re able to install the required packages for mod_mono
. Run the following command:
apt-get install mono-apache-server2 libapache2-mod-mono libmono-i18n2.0-cil
When the installation process completes start Apache with the following command:
/etc/init.d/apache2 start
Configure Apache
We recommend using name-based virtual hosts for web hosting. Refer to the Apache documentation for setting up Name-based virtual hosts .
Recent versions of mod_mono
utilize the AutoHosting
method of application deployment. This allows non-privileged users to deploy new applications without modifying Apache configuration files. While this provides great flexibility, it may also present a security risk. As a result, mod_mono
must be enabled on a per-virtual host basis.
For the sake of this guide, we’re going to create a site on the root of our example domain, example.com
. If you already have an Apache configuration for the root of your site, you will need to modify your existing virtual host file or create a new one on a subdomain of your site. Create the virtual host file, taking the following example virtual host configuration and modifying it to suit your needs. You may also use the Mod_Mono Configuration Generator
to generate your own custom configuration.
- File: /etc/apache2/sites-available/example.com
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
<VirtualHost *:80> ServerName example.com ServerAdmin admin@example.com ServerAlias www.example.com DocumentRoot /srv/www/example.com/public_html ErrorLog /srv/www/example.com/logs/error.log CustomLog /srv/www/example.com/logs/access.log combined MonoServerPath example.com "/usr/bin/mod-mono-server2" MonoDebug example.com true MonoSetEnv example.com MONO_IOMAP=all MonoApplications example.com "/:/srv/www/example.com/public_html" <Location "/"> Allow from all Order allow,deny MonoSetServerAlias example.com SetHandler mono SetOutputFilter DEFLATE SetEnvIfNoCase Request_URI "\.(?:gif|jpe?g|png)$" no-gzip dont-vary </Location> <IfModule mod_deflate.c> AddOutputFilterByType DEFLATE text/html text/plain text/xml text/javascript </IfModule> </VirtualHost>
Save and close the file, and create the directories referenced in the DocumentRoot
and ErrorLog
directive:
mkdir -p /srv/www/example.com/public_html
mkdir /srv/www/example.com/logs
Enable the site by running the a2ensite
command:
a2ensite example.com
Since we have modified the virtual host configuration, Apache must be reloaded:
/etc/init.d/apache2 reload
Note: Should you restart Apache in the future, you will see an error that will look similar to this:
[crit] (13)Permission denied: Failed to attach to existing dashboard,
and removing dashboard file '/tmp/mod_mono_dashboard_XXGLOBAL_1' failed
(Operation not permitted). Further action impossible.
You can safely ignore this warning, as it won’t affect deployment using the methods explained in this guide.
Installing MySQL Connector/Net for ASP.NET
This section assumes that you already have a functioning MySQL installation. Please refer to our MySQL Installation Guide for more detailed instructions for installing MySQL, otherwise issue the following command:
apt-get install mysql-server
In order for your ASP.NET application to communicate properly with your MySQL server, you must install the MySQL Connector/Net driver. The following commands download and install the 6.2.3 version of the connector. Check the MySQL Upstream to ensure that this the latest version of the plugin:
cd /opt/
wget http://dev.mysql.com/get/Downloads/Connector-Net/mysql-connector-net-6.2.3-noinstall.zip/from/http://mysql.mirrors.pair.com/
unzip -d mysqlConnector mysql-connector-net-6.2.3-noinstall.zip
cd mysqlConnector
gacutil -i mysql.data.dll
gacutil -i mysql.web.dll
Creating a Database to Test the MySQL Connector
Now that the MySQL Connector has been installed, you should test it by creating a sample database and a test table. First you must log in to your MySQL DBMS:
mysql -u root -p
Next you must create the sample table. Issue the following commands at the MySQL prompt:
CREATE DATABASE sample;
USE sample;
CREATE TABLE test (id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(25));
INSERT INTO sample.test VALUES (null, 'Lucy');
INSERT INTO sample.test VALUES (null, 'Ivan');
INSERT INTO sample.test VALUES (null, 'Nicole');
INSERT INTO sample.test VALUES (null, 'Ursula');
INSERT INTO sample.test VALUES (null, 'Xavier');
Finally you must create a test user named “testuser” and give that user access to the newly created sample database:
CREATE USER 'testuser'@'localhost' IDENTIFIED BY 'somepassword';
GRANT ALL PRIVILEGES ON sample.* TO 'testuser'@'localhost';
FLUSH PRIVILEGES;
Creating a Simple ASP.NET Application
Now that you have created a sample database, you can test your installation with the following test page. This will not only test your Mono installation but it will also will test your MySQL connector configuration. First create a file called testdb.aspx
in your DocumentRoot
and paste the text below into it. Be sure to change the User ID
and Password
to match what you specified above.
- File: /srv/www/example.com/public_html/testdb.aspx
<%@ Page Language="C#" %> <%@ Import Namespace="System.Data" %> <%@ Import Namespace="MySql.Data.MySqlClient" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>ASP and MySQL Test Page</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <script runat="server"> private void Page_Load(Object sender, EventArgs e) { string connectionString = "Server=127.0.0.1;Database=sample;User ID=testuser;Password=somepassword;Pooling=false;"; MySqlConnection dbcon = new MySqlConnection(connectionString); dbcon.Open(); MySqlDataAdapter adapter = new MySqlDataAdapter("SELECT * FROM test", dbcon); DataSet ds = new DataSet(); adapter.Fill(ds, "result"); dbcon.Close(); dbcon = null; SampleControl.DataSource = ds.Tables["result"]; SampleControl.DataBind(); } </script> </head> <body> <h1>Testing Sample Database</h1> <asp:DataGrid runat="server" id="SampleControl" /> </body> </html>
Next you will need to create a web.config
file. You can copy and paste the example below. Please note that Custom Errors
have been turned off in this web.config for debugging purposes. The customErrors mode
line should be removed in a production environment.
- File: /srv/www/example.com/public_html/web.config
1 2 3 4 5 6 7 8 9 10
<configuration> <system.web> <customErrors mode="Off"/> <compilation> <assemblies> <add assembly="MySql.Data"/> </assemblies> </compilation> </system.web> </configuration>
Visit the testdb.aspx
file in a web browser. If you see the text “Testing Sample Databases” in your browser with the information that you inserted into the database above, you now have a functioning mod_mono
installation and can continue with the development and deployment of your own application!
More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on