So if you want to play around with AWS for free, you have to roll Linux. If you want to host ASP.NET MVC3 on AWS Linux, there’s a few steps you need to take. For this post, I’ll talk about some of the AWS services that can get you started along with how to install and configure your environment for hosting ASP.NET MVC3 applications with Linux and Mono.

Disclaimer:

Before you try any of this, carefully read all the terms and conditions regarding Amazon Web Services. Review their pricing structure for every service you plan to use and the qualifying restrictions for the free tier. While their pricing structure is very competitive, it’s also very complicated. Be sure to fully understand what services you enable before doing it. Payment information is required to setup your AWS account, but you will only be charged when you use services that are not free. I am not responsible for any fees you may incur while using AWS services.

Conventions Used in This Article

Intended Audience

I’m writing this post for people who are mostly familiar with Windows environments and maybe have some experience with Linux. I may over-explain a few concepts like using SSH or tab completion, which mainly target the Windows folks who may have never seen this before. Otherwise, this post can be used as a reference guide to AWS and using Mono Web hosting in general. We will be using the default MVC 3 application as our sample, which might be interesting if you haven’t worked with it yet. If you’ve never worked with Mono web hosting before, always start with something simple and familiar. I wouldn’t recommend trying to take your massive, enterprise, e-commerce solution and running it straight up on Mono without expecting a few hiccups.  The MoMA tool will be useful for migrating assemblies since it identifies functionality not yet supported by Mono in your assemblies.

Keystrokes

There are a few conventions used throughout this tutorial. I’ll indicate keystrokes with {} characters, like in the example: {Ctrl} for a Control keystroke. I’ll hyphenate key combos like {Ctrl-D} for Control and D pressed simultaneously. And I’ll separate them for consecutive keystrokes: {Ctrl}{D} for Control then D.

Tab Completion

Another useful tip I’ll sometimes mention is when using the bash shell, you can type a segment of a directory or file name and press {TAB} to complete it. It will complete to the next unique segment. So if there are two files with similar names, it will complete the statement for the common portions of the names and wait for input. You can add the next unique character and press {TAB} again to make it go further. This is very useful when entering long paths or filenames from the command line. For example to script named install_mono-2.10.5.sh you can simply type:

./in{TAB}

Wait for the completion, then if it’s correct, {ENTER} to execute it.  Sometimes you’ll have to add a few extra characters to help it out.  Any path or git branch argument (and probably many other things) in Linux use this functionality.

Linux Command Line

As always with Linux command line, if you want to know how a specific command works, you can always check its manual pages by entering: “man <command>”   For example to see the manual for ssh, you can enter “man ssh”.  To exit the manual, just hit {Q}.

Amazon Web Services

Amazon Web Services (AWS) is a lot like an Ad-hoc enterprise infrastructure. You pick and choose the components you want and put them together in the arrangement of your choice. Every service comes with a cost, so you weigh how you design your infrastructure based on your needs. The main two services we’ll use to get started include EC2 (Elastic Cloud Computing) using EBS (Elastic Block Storage) for its local file system and S3 Storage Service as our static content storage (and delivery).

Elastic Cloud Computing (EC2)

EC2 is simply server that and provide any service we want. It’s computing on demand and you pay by the hour. For smaller environments (like this walkthrough), we’ll fire up one micro instance for both database and web server; while in larger environments, you might setup a pool of database servers, a pool of application servers with horizontal scaling in mind. With EC2 you have the option of using the built-in instance storage (usually about 160GB for paid servers) or using the Elastic Block Storage (EBS) service. EBS allows for a persistent (shared) storage for your instances. You can clone them into new servers or snapshot instances on existing servers.

Amazon Simple Storage Service (S3) & CloudFront

The S3 service provides centralized storage for all your applications. S3 is accessible from outside the Amazon network and the price is pretty competitive starting roughly around $0.14 USD/GB/month. Using this service is not required, but if you have an application with a lot of local assets, this is a pretty good option to keep them on the AWS network. You can also expose your files in S3 to the public essentially turning it into a static file web server. If you need a more responsive edge network, then S3 will serve as a data source for the CloudFront service and deploy your assets to edge locations around the world.

Tools

In order to use AWS on Linux, you’ll need an interactive SSH client and some common Linux utilities like tar, gzip, etc. For those of you Linux/Mac users, these tools are likely already setup on your machines. However, those of you Windows folks (like me) will need to install a few things.

MsysGit comes with all these utilities nicely packaged. Msys is a set of recompiled GNU utilities for Windows. It enables a nearly identical bash command line shell for Windows as Linux, and they run natively. It also comes with openSSH and SCP which come in extremely useful when connecting to servers or moving files around between Windows and Linux.

Putty is another great interactive SSH utility, and FileZilla is a great graphical file transfer client, which works with SSH. I commonly bounce between all these tools in my environments. If you want to use Putty with your AWS server, you’ll also need the PuttyGen utility available on Putty’s website. This will create a private key that wraps your openSSH based key for use with Putty and FileZilla.

Finally, if you want to use AWS services programmatically, you of course will need to download the AWS SDK.  Mac/Linux users can scroll to the bottom of the screen and download the “DLLs and Samples” version that is packaged in a ZIP for Mono.

Required Windows tools for this walk-through:

• MsysGit installer  – During install, make sure you enable the Windows Explorer shell context menu for Git Bash Here.

Setup EC2 Instance

Before you get started setting up a new EC2 instance, you need to register an AWS account. This will require a credit card. If you’re a new customer or comply with their terms and conditions for the free tier, then you don’t need to worry about being charged fees for usage. Registration takes a little while. Eventually, you’ll receive an email stating your account is active and ready to go.

Launch New Instance

Sign into your AWS Management Console and enter the EC2 section.  When creating a new EC2 instance, we’re first going to find the Amazon Machine Image (AMI) that we want to use for our new server. Canonical provides a few pre-built ones for different versions of Ubuntu and they occasionally release updated AMI’s as updates are released.  I chose to use the most recent (at the time of this post) Lucid (10.04 LTS) build.

To get started, click Launch New Instance in the top left. First, choose the Community AMI’s tab and then search for ami-61be7908.  Also, watch for the star that indicates "free tier” server. Make sure you choose a free tier AMI!

Step through the setup wizard for your new AMI. I used mostly defaults to ensure the free tier shown here. Click each image for an enlarged screenshot.

The important thing here is that we’re choosing a micro (free tier instance). Starting out, I would open up just your web ports 80 and 22. When you finish the wizard, your instance will automatically start up.

During step three, you will create a new key pair if you haven’t already created one. You will need to download the key file to your local machine and place it somewhere easily accessible for you to use from a command line. (In my case, I saved to the ~/.ssh folder which translates to C:\Users\<username>\.ssh in Windows 7.

Setup an Elastic IP

Before we connect to the new server, we also need to setup an Elastic IP.  Elastic IPs act similar to static IPs except when you’re done using them, Amazon will release it back into the pool for someone else to use.  This will allow you to shutdown your server or reboot your server and still maintain the same IP. Using this service is free as long as you have a running instance associated with it; otherwise, Amazon will charge for its use to discourage wasting unused IP allocations on their network.

Since we have a new EC2 instance available and running, go ahead and allocate an Elastic IP. To do this, make sure you’re still in the EC2 section of AWS dashboard and click the Elastic IPs link under the left navigation labeled: Network & Security.  Click the button on the to, “Allocation New Address”. Select the EC2 option and click “Yes, Allocate.”  You will now have a dedicated IP in your list. Select the row and then click “Associate Address.” Choose the instance we just setup, and you’re done! One caveat to take note of is that shutting down the server will disassociate the address. So when you boot it back up, you will need to re-associate the address.  Rebooting the server will not disassociate the address.

Connect to Your Server

Now that you’ve setup your new EC2 instance and you’ve configured your Elastic IP to route to your instance, you can now make a connection to your new server.

NOTE: Typically you can setup a DNS host record to resolve to your Elastic IP simplifying communication with your server. Naturally, this is what you would do when setting it up as a web server.  In this case since we’re just experimenting, you can setup an easy unknown name like test.yourdomain.com just so you don’t have to continually refer to your IP address in command line.

SSH in the Linux world is like the Swiss army knife for admins.  You can use SSH to connect to an interactive terminal, transfer files, or even tunnel traffic through its connection. It’s also encrypted with a public/private key pair (typically RSA). When you created the key on Amazon, you essentially generated the public/private key pair and you downloaded the public key.  SSH will use that public to authenticate your connection against a pre-setup user account on the server.

Have your key file handy. Earlier I suggested you place this in your home .ssh directory ~/.ssh or on Windows 7, C:\Users\<username>\.ssh\.  Right click on any directory with Windows Explorer and open an Git Bash. Then go to your .ssh directory by entering: “cd ~/.ssh”.  This should place you in the same directory that we stored the key file for AWS making it very easy to refer to during this walkthrough. In the sample below, we called this file “mykey.pem”. Call it whatever you want.

Enter:

ssh aws.yourdns.com –l ubuntu -i mykey.pem

NOTE: Don’t forget the tab completion here. A shortcut for this is to enter the command below. (Of course this is assuming you’re in the same directory as the mykey.pem file. 

ssh aws.yourdns.com –l ubuntu -i my{TAB}

You should see a busy welcome screen informing you about some basic info about your server. It will also let you know if you’re running the most recent AMI.  Having the most recent AMI is not very important. With the built-in aptitude package manager, your server can easily stay current even running an older AMI.

Linux domU- 2.6.32-318-ec2 #38-Ubuntu SMP Thu Sep 1 17:54:33 UTC 2011 i686 GNU/Linux
Ubuntu 10.04.3 LTS

Welcome to Ubuntu!
 * Documentation:  https://help.ubuntu.com/

  System information as of Tue Nov  8 19:48:48 UTC 2011

  System load:  0.0               Processes:           68
  Usage of /:   37.6% of 7.87GB   Users logged in:     0
  Memory usage: 41%               IP address for eth0: 10.208.195.158
  Swap usage:   0%

  Graph this data and manage this system at https://landscape.canonical.com/
---------------------------------------------------------------------
At the moment, only the core of the system is installed. To tune the
system to your needs, you can choose to install one or more
predefined collections of software by running the following
command:

   sudo tasksel --section server
---------------------------------------------------------------------

8 packages can be updated.
7 updates are security updates.

A newer build of the Ubuntu lucid server image is available.
It is named 'release' and has build serial '20110930'.
Last login: Mon Nov  7 21:31:53 2011 from 75.81.113.113

As you can see, I have a few packages that are available for update. So the first thing I like to do is immediately update the server. Do that with two commands. Apt-get update and apt-get upgrade. Update will re-sync the package cache for the local repositories. Upgrade will actually download and install the updated packages onto your system. Dist-Upgrade, another form of upgrade, will force update all new packages regardless of dependencies. This is typically something you’ll use when you start with a fresh server. After that, the normal “upgrade” should work fine. You can combine these commands into one by concatenating them with “&&”.

sudo apt-get update && sudo apt-get dist-upgrade -y

This will update the repositories; and if successful, will continue to the upgrade command and install the updates.  The option “-y” simply instructs the upgrade to automatically answer yes to installing package updates.  We’re running the command with sudo to temporarily enable root privileges. We’re “su” “doing” the command.

Install Mono & Apache

Now that we’ve updated the system we can continue to install all the necessary packages for the web server. I’m choosing to use Badgerports for the Mono install. Optionally, you can compile and install your own (sometimes more recent) version of Mono, but Badgerports is very convenient and easy to use.  At the same time, we’ll install Apache.  Enter these commands sequentially (one per line)

wget http://badgerports.org/directhex.ppa.asc
sudo apt-key add directhex.ppa.asc
sudo apt-get install python-software-properties
sudo add-apt-repository 'deb http://ppa.launchpad.net/directhex/ppa/ubuntu lucid main'
sudo apt-get update
sudo apt-get install mono-apache-server4 mono-devel libapache2-mod-mono 

Setup Web Folder

Now configure the directory where we’ll place the web files. Enter the following commands to create the directory and set its ownership and permissions.

cd /srv
sudo mkdir www
cd www
sudo mkdir default
sudo chown www-data:www-data default
sudo chmod 755 default

Configure Apache & Virtual Host

Finally, setup the apache virtual host to run our website.  We’ll start by creating our virtual host configuration file that enables the 4.0 mono server for the web directory we just setup. We’ll than set it up nicely with the debian/ubuntu environment so we can easily disable and enable it.  For this sample, I used mono-project’s mod_mono configuration tool as a starting point. I then switched its server command to mod-mono-server4 (for 4.0 runtime), and I also changed its DocumentRoot to use the directory we setup.

<VirtualHost *:80>
  ServerName my-mono-server.somewhere.com
  ServerAdmin web-admin@my-mono-server.somewhere.com
  DocumentRoot /srv/www/default
  MonoServerPath my-mono-server.somewhere.com "/usr/bin/mod-mono-server4"
  MonoDebug my-mono-server.somewhere.com true
  MonoSetEnv my-mono-server.somewhere.com MONO_IOMAP=all
  MonoApplications my-mono-server.somewhere.com "/:/srv/www/default"

  <Location "/">
    Allow from all
    Order allow,deny
    MonoSetServerAlias my-mono-server.somewhere.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>

We’re going to use the local clipboard to copy and paste the contents into VIM through the msys window. With the default MSysGit client, it uses a Windows “cmd” shell so you can right click, “Paste” or enable quick edit mode to paste into the window.  While working in VIM, if you have an problems with keystrokes, just hit {Esc} a couple times and you should be able to re-enable insert mode by pressing {i} once. Enter the following to open a new file in VIM.

cd /etc/apache2/sites-available
sudo vi mono-default

#copy the contents above and paste them into the new file
{i}{Then paste - right click the window and select paste}
{Esc}:wq{Enter}

Now we can create a symbolic link to this file from the enabled directory.

cd /etc/apache2/sites-enabled
sudo rm 000-default
sudo ln -s /etc/apache2/sites-available/mono-default 000-mono

Install Trusted Certificate Authorities

If we want to use the AWS tools in our application, we’ll need to first install the trusted keys. We’ll use the mozroots tool to do that. We’ll use “sudo –u www-data” to run mozroots as the www-data user.

Enter:

sudo –u www-data mozroots --import –sync 

As a simple test to ensure the basic configuration is working, we can move the normal default web page into our new directory and then make a request against it.

sudo mv /var/www/index.html /srv/www/default
sudo vi /srv/www/default/index.html 

# arrow down a couple lines to content
# press {i} then enter something. just to make it a little different
{Esc}:wq{enter}

# restart the web server sudo service apache2 restart 

If the web server restart reported “OK” then make a request against your server (from your local machine) to test the web server configuration. Open a browser and browse to http://<your-host-name/index.html.  You should see your slightly modified default page. Now we can continue on to building out the default MVC3 web application and test that.

If the web server did not restart okay, read the messages that were reported. Also, if you’re not seeing anything there you can always refer back to the apache logs located at: /var/log/apache2/error.log.  If anything goes wrong throughout this entire process, always check the end of that file.

Deploy your first site

Create and Publish a New MVC 3 Project

Finally… We’re ready to deploy a real .NET MVC3 application on Linux. We’re going to be doing a typical BIN deployment of MVC 3. I have detailed this out in another blog post and covered some of the potential issues you could run into while BIN deploying an MVC 3 project to Mono.  Feel free to refer to that post if you having any problems. Lets get started here by creating a new project.

Open Visual Studio and create a new Project. Choose .NET Framework 4, then ASP.NET MVC 3 Web Application. Choose Internet Application template. Then select the Razor view engine and optionally the HTML5 semantic markup.  We’re just going to roll this application as-is. You do not need to create the unit test project.

Under the Solution Explorer, expand the References node. We need to enable Copy Local on a few necessary assemblies for this to work in Mono. Go to properties of the following assemblies and set their Copy Local option to True: System.Web.Helpers, System.Web.Mvc, System.Web.Routing, and System.Web.WebPages.

Now publish the project. Select the Build menu, then Publish AWSMonoSample.Web. Choose Publish Method: File System and select a local directory for copying the published files. I also typically select “Delete all existing files prior to publish” to ensure a clean publish directory.  Then click Publish. (In my sample, I’m publishing to C:\temp\AWSMonoSample.Web).

To deploy an MVC 3 site, we’ll also need to collect a few more MVC 3 and Razor dependencies. Browse to: Program Files\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\Assemblies directory and grab System.Web.WebPages.Deployment.dll, System.Web.WebPages.Razor.dll, and System.Web.Razor.dll. DO NOT grab any other assemblies. Place all these assemblies in your published folder’s bin directory.  You should only have to do this once, but it’s always a caveat of deploying MVC 3 to Mono on a new server.

Deploy Published Files to Your Server

Now we can upload the files.  Since AWS by default is public key authenticated, we’re going to use the manual command-line method. Once you understand public key authentication a little better, tools like FileZilla or WinSCP will work a little easier (if you like the GUI interface thing).

So to start, open My Computer / Windows Explorer and browse to your published directory (C:\temp\AWSMonoSample.Web for this example). Then right click on that directory and select Git Bash Here from the context menu. You should now be looking at a local BASH command line with your working directory being the deployment folder we just setup.

For this deployment, we’re going to first package the files into a gzipped tarball, then we’re going to “scp” upload it to our server. From that point, we’ll ssh back into our server and extract the files in the web directory we setup earlier.

So enter:

$ tar -zcvf aws.tar.gz *
$ scp aws.tar.gz ubuntu@your-aws-hostname: -i ~/.ssh/mykey.pem

NOTE: Replace the hostname with the one you have setup for your AWS EC2 instance. Also replace your keyfile path with the one you have setup locally for AWS.

You should see a successful transfer. Now you can connect to your server and extract the files in place. Open a new (or use an existing SSH connection if you still have one open). Start from your home directory with the command: “cd ~/”.

ssh ubuntu@your-aws-hostname -i ~/.ssh/mykey.pem
mv aws.tar.gz /srv/www/default
rm index.html   #remove test from earlier
tar -zxvf aws.tar.gz
rm aws.tar.gz   #optional cleanup

sudo service apache2 restart      #for a fresh start

That’s it! Now make a request against your server, and you should see the new MVC 3 sample website displayed! Keep in mind the membership is not wired up and the registration form may blow up on you (as it also would in Windows); but otherwise, the basic MVC stuff works including model validation.

Useful Links

• Amazon Web Services
• Mono Project
• Mono Configuration Tool
• MsysGit
• Hanselman’s BIN Deploy MVC3 post
• Badgerports
• Ubuntu

System.InvalidOperationException: The view ‘Index’ or its master was not found or no view engine supports the searched locations. The following locations were searched: ~/Areas/Manage/Views/Dashboard/Index.aspx ~/Areas/Manage/Views/Dashboard/Index.ascx ~/Areas/Manage/Views/Shared/Index.aspx ~/Areas/Manage/Views/Shared/Index.ascx ~/Views/Dashboard/Index.aspx ~/Views/Dashboard/Index.ascx ~/Views/Shared/Index.aspx ~/Views/Shared/Index.ascx ~/Areas/Manage/Views/Dashboard/Index.cshtml ~/Areas/Manage/Views/Dashboard/Index.vbhtml ~/Areas/Manage/Views/Shared/Index.cshtml ~/Areas/Manage/Views/Shared/Index.vbhtml ~/Views/Dashboard/Index.cshtml ~/Views/Dashboard/Index.vbhtml ~/Views/Shared/Index.cshtml ~/Views/Shared/Index.vbhtml

I’m saying this purely by observation. But MVC3 (or maybe the Mono runtime) seems to group compiled view code by controller. I was able to figure out that ALL ViewResult actions failed under this specific controller. It turns out I had one character out of place in my Razor syntax. With that one syntactical flaw, all the views under that controller could not compile and the only reasonable exception that could be thrown was the one above. The windows runtime seems to ignore this (maybe because it compiles them individually; I don’t know). In my case, I was trying to render one view when another view was causing the problem.

So if you see this exception and everything seems to be correct, start sifting through your recent View changes to see if anything you did broke the view syntax. So you can get a little laugh, here’s my goof up:

The indicated ‘@’ symbol is not necessary when continuing additional statements.

Enjoy!

I just updated the 2.10 script to use the latest 2.10.8 Mono install.

Install

mkdir mono-2.10
cd mono-2.10
wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_mono-2.10.sh
chmod 755 install_mono-2.10.sh
./install_mono-2.10.sh

Enjoy!

Update 12/30/2011 – Updated Mono 2.10.6 to 2.10.8

Update 10/16/2011 – Updated Mono 2.10.5 to 2.10.6

Update 8/31/2011 – Updated Mono 2.10.4 to 2.10.5

Update 8/11/2011 – Updated Mono 2.10.3 to 2.10.4 for minor update.

I dug around a little to figure this out. Hopefully this will clarify all the steps required to get an MVC 3 Razor site running on Mono. The main pitfall I ran into was gathering the additional dependencies and excluding Microsoft.Web.Infrastructure assembly from my deployment. Overall though it’s not too difficult to deploy your MVC3 app.

In Summary:

1. Install Mono
2. BIN Deploy Website
3. Configure Apache (or Xsp environment)
4. Fire Up Your Server
5. Errors You Might See

Install Mono

If you haven’t done this yet, go grab it from the Mono downloads page. You need to run at least Mono 2.10, preferably the latest release (2.10.2). For Ubuntu you can use the badgerports; or for Ubuntu, compile from source using a bash script I created. (Skip the MonoDevelop install).

BIN Deploy Your Website

For this, I just performed a traditional “Publish” from Visual Studio to a file system directory. Be sure to set these references to “copy local.”

• System.Web.Mvc
• System.Web.Helpers
• System.Web.Routing

BIN Deploy Additional MVC3/Razor Dependencies

Just like Scott Hanselman mentions in his BIN deployment post, add these additional libraries found in the MVC3 RTM. On Windows, they install to C:\Program Files\Asp.Net.

• System.Web.Razor
• System.Web.WebPages
• System.Web.WebPages.Razor
• System.Web.WebPages.Deployment

NOTE: Do NOT copy the Microsoft.Web.Infrastructure assembly.  This assembly has been rebuilt in the mono library and will already be available to your app. 

Configure Apache/XSP

Once you have Mono runtime installed, setup your apache virtual host configuration. Setup a virtual host to use mod-mono-server4. If you installed Mono with a custom prefix (like my script above), then be sure and setup your virtual host environment. Here’s a sample virtual host configuration using the Mono install prefix of, “/opt/mono-2.10”.

<VirtualHost *:80>
  ServerName yourhostname

  DocumentRoot /srv/www/mvc3

  <Directory />
    Options FollowSymLinks
  </Directory>

  MonoServerPath mvc3 "/opt/mono-2.10/bin/mod-mono-server4"

  #optional debug mode
  MonoDebug mvc3 true 

  #be sure and set the prefixed mono paths here
  MonoSetEnv mvc3 MONO_IOMAP=all;PATH=/opt/mono-2.10/bin:$PATH;LD_LIBRARY_PATH=/opt/mono-2.10/lib:$LD_LIBRARY_PATH;  

  MonoApplications mvc3 "/:/srv/www/mvc3"
  <Location />
    Allow from all
    Order allow,deny
    MonoSetServerAlias mvc3
    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>

For running XSP manually, setup your shell environment with the correct prefix. Here’s a sample bash script.

#!/bin/bash
MONO_PREFIX=/opt/mono-2.10
GNOME_PREFIX=/usr
export DYLD_LIBRARY_FALLBACK_PATH=/lib:
export LD_LIBRARY_PATH=/lib:/opt/mono-2.10/lib:
export C_INCLUDE_PATH=/include:/include
export ACLOCAL_PATH=/share/aclocal
export PKG_CONFIG_PATH=/lib/pkgconfig:/lib/pkgconfig
export PATH=/bin:/opt/mono-2.10/bin:$PATH

When you’re ready to fire up Xsp4: save the script above to a file (in this case env.sh), enter a terminal, change your working directory to the web directory and enter the following:

$ source env.sh
$ xsp4

Fire It Up

Once everything has been deployed, fire up xsp4 or restart your apache2, all should be working.

Errors You Might See

• System.Security.SecurityException: No access to the given key.
  • Delete Microsoft.Web.Infrastructure.dll from you bin directory.
• No response from web server on request, but you do see errors in the log /var/log/apache2/error.log
  • Check to make sure all your dependencies are present in the bin folder and apache has read/execute access to them. (Ubuntu: www-data group).  Also read through the errors at the end of the file and see if something else is causing the problem. Sometimes I rename/delete error.log and then restart the server for a fresh log.
• File request returns a 404 or asp.net missing assembly exception (but the file(s) actually exists)
  • Check your file permissions and make sure www-data group has read access to the files and read/execute to the directories involved.
  • find web-directory -type f exec chmod 664 {} \;
  • find web-directory -type d -exec chmod 775 {} \;
• Cannot find View…  (but it really does exist…)
• • There are a few things that cause this. 
  • File permissions; make sure www-data can read the web files
  • missing Web.config (especially under ~/Views); this is what informs the compiler how to build the view templates.
  • Syntax error in a view (may cause other views not to render returning this error).
  • Missing assemblies (make sure you bin deploy the site with all the necessary Razor and WebPages dlls. Do not deploy Microsoft.Web.Infrastructure.
  • Layout/Master page being used doesn’t exist.
  • Getting: “The classes in the module cannot be loaded”,   Just delete System.Web.WebPages.Administration.dll from your local bin directory. (not required for this).

Steps to Install

1. Install Mono 2.10
2. Install MonoDevelop
3. Use the launcher script to run MonoDevelop.

Installing Mono

If you already have mono installed or are upgrading, skip this step. This will install the latest Mono 2.10.2 to the prefix directory /opt/mono-2.10.

NOTE: You can optionally change the PREFIX value in the beginning of the script to install to a different location.

Ubuntu

mkdir mono-2.10
cd mono-2.10
wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_mono-2.10.sh
chmod 755 install_mono-2.10.sh
./install_mono-2.10.sh

Fedora (< F15)

NOTE: Fedora 15 is packaged with Mono 2.10.2 and can be easily installed with YUM.
yum install mono xsp mono-devel

mkdir mono-2.10
cd mono-2.10
wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_mono-2.10.sh
chmod 755 install_mono-2.10.sh
su
./install_mono-2.10.sh

If all is well, enter:

/opt/mono-2.10/bin/mono -V

And you should get a display of Mono 2.10.2

Mono JIT compiler version 2.10.2 (tarball Mon May 23 14:23:52 CDT 2011)
Copyright (C) 2002-2011 Novell, Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  x86
        Disabled:      none
        Misc:          softdebug
        LLVM:          supported, not enabled.
        GC:            Included Boehm (with typed GC and Parallel Mark)

Installing MonoDevelop Beta 3

If you did not use my script for Beta 2, then you can easily install a new fresh copy of Beta 3.

NOTE: I’m still working on a script for Fedora 15 (or any system installed w/ Gnome 3) due to the newer dependencies.

Ubuntu

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_monodevelop-2.5.92.sh
chmod 755 install_monodevelop-2.5.92.sh
./install_monodevelop-2.5.92.sh

Fedora (<15)

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_monodevelop-2.5.92.sh
chmod 755 install_monodevelop-2.5.92.sh
su
./install_monodevelop-2.5.92.sh

Upgrade Beta 2 to Beta 3

Upgrade the existing version. Download this script to the same directory you installed Beta 2. It will uninstall the older version using the original install source that should still be there.

Ubuntu

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/upgrade-monodevelop-2.5.91-to-2.5.92.sh
chmod 755 upgrade-monodevelop-2.5.91-to-2.5.92.sh
./upgrade-monodevelop-2.5.91-to-2.5.92.sh

Fedora (<15)

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/upgrade-monodevelop-2.5.91-to-2.5.92.sh
chmod 755 upgrade-monodevelop-2.5.91-to-2.5.92.sh
su
./upgrade-monodevelop-2.5.91-to-2.5.92.sh

Enjoy!

This work is licensed under the Creative Commons Attribution 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.

Disclaimer

First of all, I should mention in big, giant font:  "RUN THIS AT YOUR OWN RISK."  I highly recommend getting familiar with the build process before trying this out. These scripts are only meant to be a tool to help you out. They're not intended to be an end all solution for installing these packages. Feel free to modify the scripts to make them work for you.  Also, if you're just interested in installing stable Mono 2.10 w/ MonoDevelop 2.4 on Ubuntu, checkout the Badgerports; they've already packaged this thing up. It's a 1000x easier to do. 

Steps to Install

1. Install Mono 2.10.
2. Install MonoDevelop
3. Use the launcher script to run MonoDevelop.

In Detail – Installing Mono

This install, will install the latest Mono 2.10.1 to the prefix directory /opt/mono-2.10.

NOTE: If you’ve already installed 2.10, you can skip this step or you can change the PREFIX value in the beginning of the script to install to a different location.

Ubuntu

mkdir mono-2.10
cd mono-2.10
wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_mono-2.10.sh
chmod 755 install_mono-2.10.sh
./install_mono-2.10.sh

Fedora

mkdir mono-2.10
cd mono-2.10
wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_mono-2.10.sh
chmod 755 install_mono-2.10.sh
./install_mono-2.10.sh

This new script will stop if anything goes wrong. If you have a problem, usually the error or message will display a few lines above the prompt. You Windows folks, can press Shift-PageUp to scroll the screen up and see more information. Usually errors are caused by missing development packages on the system, missing environment settings or some incompatibility.  Google will come in very handy for most of these.

NOTE: I did notice a problem during the "make install" of xsp. However, the mod-mono-server programs did install fine. For now, ignore this and continue. 

If all is well, you should be able to enter:

/opt/mono-2.10/bin/mono -V

And you should get a display of Mono 2.10.1

Mono JIT compiler version 2.10.1 (tarball Tue Mar  8 15:01:43 CST 2011)
Copyright (C) 2002-2011 Novell, Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  x86
        Disabled:      none
        Misc:          softdebug
        LLVM:          supported, not enabled.
        GC:            Included Boehm (with typed GC and Parallel Mark)

Installing MonoDevelop 2.4.2

NOTE: If you want to try the beta 2.6 version, skip the 2.4 install and go straight to the next one.

Now the fun part. Download and run another script to install the tools. If you’re installing to a different prefix, make sure you set the correct one at the beginning of the script before you run it.  The script will install the sources found on the MonoDevelop download page.

Ubuntu

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_monodevelop-2.4.2.sh
chmod 755 install_monodevelop-2.4.2.sh
./install_monodevelop-2.4.2.sh

Fedora

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_monodevelop-2.4.2.sh
chmod 755 install_monodevelop-2.4.2.sh
./install_monodevelop-2.4.2.sh

After it installs, run the monodevelop-launcher.sh file generated in the same directory containing the install scripts and you’ll be good to go.

Installing MonoDevelop Beta 2.6 Instead

This script is totally experimental and will install to the SAME location as the 2.4 version unless you change the prefix.

Ubuntu

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_monodevelop-2.5.90.sh
chmod 755 install_monodevelop-2.5.90.sh
./install_monodevelop-2.5.90.sh

Fedora

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_monodevelop-2.5.90.sh
chmod 755 install_monodevelop-2.5.90.sh
./install_monodevelop-2.5.90.sh

How it works – A little bit of VooDoo

So I’ve been experimenting with a new bash script that will install MonoDevelop on Ubuntu for awhile now, but I always ran into an issue with the current source packages that caused gnome-sharp not to build. That throws a wrench in a script when you want all the packages to build all at once. The problem in gnome-sharp was a broken test that used an old reference no longer packaged with the current version. So it required a little manual care before you could build it. Glancing at the discussion here, I decided to roll a real simple C# application that would automatically comment those lines out for me.

But how do you deploy such a creature with just a bash script?  Well… here’s the voodoo.  I removed all the whitespace from the C# code I wrote and embedded it as a bash string. Then I echo/piped it to a text file, compiled it and used it within the bash script. You’ll notice if you watch the system while you’re installing it, that it creates a program called “comment-lines.exe”.  (Feel free to use it). The bash script will auto-remove it when the install succeeds, but you can comment out the cleanup line and re-use it. You can also fine the original source for the program here.

So that’s it!  I hope these scripts help you out. They may seem a little more frustrating than the old ones since they actually stop when some thing isn’t working, but hopefully it’s all for the better.  Let me know how they work for you.

I just updated the bash install script for Mono 2.10. Thanks to @Marv for the Ubuntu script and heads up that 2.10 was released. This script is mainly intended for use with linux/apache web servers. It will install Mono, GTK, OpenGDI, XSP, and Mod_Mono. For Mono Develop, read through the Building Mono Develop page [mono-project.com], which will require a few additional packages not included in this script.

To install for Ubuntu:

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_mono-2.10.sh
chmod 755 install_mono-2.10.sh
./install_mono-2.10.sh

To install for Fedora:

yum install wget
wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_mono-2.10.sh
chmod 755 install_mono-2.10.sh
./install_mono-2.10.sh

Again, if setting up a web server, be sure to set the VirtualHost environment up correctly with PATH & LD_LIBRARY_PATH. (here, IOMAP is optional) See configuring virtual hosts. The following line should be included in your VirtualHost configuration.

MonoSetEnv site_name MONO_IOMAP=all;PATH=/opt/mono-2.10/bin:$PATH;LD_LIBRARY_PATH=/opt/mono-2.10/lib:$LD_LIBRARY_PATH;

Update – March 15, 2011

I’m refactoring some stuff, so bare with me. Today I’m introducing a totally re-written script that will hopefully make it easier to adapt to updates in the future. So far, I’ve treated these bash scripts like I do Windows batch files. But I took some time and tried to learn a little more about writing bash scripts.  The new scripts will stop if any errors are encountered. This is good and bad.  Good because now you know something went wrong, and the errors are much easier to find. Bad (maybe) because now you know something might not have worked. Anyway, I hope the changes will help everyone.

I’ve changed all the prefixes to use the major/minor version. So 2.10.1, 2.10.2 etc, will use prefix /opt/mono-2.10. You’ll always have the option to change that if you wish to use a different prefix. There’s a single variable in the beginning of the script that sets the prefix.

Finally, there does seem to be a problem at the end of installing xsp. However, everything seems to go in okay.

Good luck!

UPDATE – March 8, 2011

Mono 2.10.1 was released Feb 25th. I updated the install script for 2.10 to use the Mono 2.10.1 package. (That was the only package updated in this version). I’ve also included an experimental upgrade script for 2.10 to 2.10.1 here. (fedora vs ubuntu use the same script). Download it to the same location of your script for 2.10 and run it.  It will uninstall just mono-2.10 and then download, compile, and re-install the new mono-2.10.1.

Enjoy!

I just committed the script for 2.8.2. This was literally a text replacement of 2.8.1. However, this one seems to work with asp.net membership out of the box; so that’s good. Anyways you can find these scripts at github.com or use the bash sequence below.

I ran through these scripts on Ubuntu 10.10 and Fedora 14 fresh installs.  I would discourage setting your default environment path to use this version and stick to using it just for Asp.Net. You can set the MonoPath in your Apache virtual host config to use this one specifically.  It will install to /opt/mono-2.8.2

Comment if you have any questions or problems.

Ubuntu

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_mono-2.8.2.sh
chmod 755 install_mono-2.8.2.sh
./install_mono-2.8.2.sh

Fedora

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_mono-2.8.2.sh
chmod 755 install_mono-2.8.2.sh
./install_mono-2.8.2.sh

Update 1/30/2011

Be sure and set the environment variables in the virtual host config to use the correct prefix. This script will install to /opt/mono-2.8.2;  So modify the MonoSetEnv line in your virtual host config: 

MonoSetEnv appName MONO_IOMAP=all;LD_LIBRARY_PATH=/opt/mono-2.8.2/lib:$LD_LIBRARY_PATH;PATH=/opt/mono-2.8.2/bin:$PATH

MONO_IOMAP=all is optional; but on by default usually. The important part is to include the other two so mod_mono knows how to find this 2.8.2 install.  Likewise, if you're running console or GUI apps w/ this version; you'll need to set your local environment to use the modified LD_LIBRARY_PATH and PATH as well. See http://www.mono-project.com/Parallel_Mono_Environments for more info. 

Update 2/20/2011

Mono 2.10 has been released and I added a new install script.

Ubuntu:

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_mono-2.8.1.sh

Fedora:

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/fedora/install_mono-2.8.1.sh

After download:

chmod 755 install_mono-2.8.1.sh
./install_mono-2.8.1.sh

If you have previously installed Mono from source, you may want to uninstall it before deleting its source. Run sudo make uninstall from each component directory you previously installed.

Update! 1/30/2011

Mono 2.8.2 has become available since this article was posted and is highly recommended due to security enhancments. Refer to install script for Mono 2.8.2 instead of 2.8. Pay close attention to your virtual host config so you use the correct mono install prefixes. Check MonoServerPath and MonoSetEnv directives below.

Setup Your Server

For our server, we’re going to setup a VM of 32 bit Ubuntu Server 10.04 LTS using VirtualBox. You can use whichever VM software you want or setup a physical server. This is just an easy sandbox system for this walkthrough. I noticed VirtualBox requires hardware virtualization for 64bit guest systems; keep that in mind if you test with a 64bit server.

I applied default configuration settings to my VM with 512 RAM and a bridged network interface so I could communicate with it directly from another machine. After that, I mounted the Ubuntu Server install ISO to the disc drive and booted it into installation.  During installation, the only package option I enabled was the OpenSSH Server (use arrows, spacebar, and tabs to move around the installer).  I’m not going to worry about other things like a web server since the Mono installer script will do that for us. Once you’ve completed the installer, unmount the ISO, boot up, and login. It defaults to using DHCP for ethernet, so find the current IP using:

ifconfig eth0

Using the IP Address listed here, connect to the box with an SSH client of your choice (I tend to use Putty or the OpenSSH client built into msysGit on Windows).  Immediately update your server. If you haven’t used “sudo” before, it will request your sudo password, which is just your normal account password you setup during install.

ssh nathan@ubuntu
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get upgrade -y

Install Mono

Once you’re updated, we can download the install script and install Mono, Apache, and dependencies.

wget --no-check-certificate https://github.com/nathanb/iws-snippets/raw/master/mono-install-scripts/ubuntu/install_mono-2.8.shchmod 755 install_mono-2.8.sh./install_mono-2.8.sh

This will re-run another update and then download, compile, and install everything required to run Mono 2.8. It will also compile and install other Mono-related items like: GTK, GDIPlus, XSP, and Mod_mono. Once it completes, update your system path and reboot. Edit “/etc/environment” and insert “/opt/mono-2.8/bin:” to the beginning of the PATH value.

Once completed, refer to this more recent post about setting up MVC, which also includes information about setting up your environment for the new install. You can test it with “mono –V”.

nathan@ubuntu:~$ mono -V
Mono JIT compiler version 2.8 (tarball Mon Nov 15 14:39:28 CST 2010)
Copyright (C) 2002-2010 Novell, Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  x86
        Disabled:      none
        Misc:          debugger softdebug
        LLVM:          supported, not enabled.
        GC:            Included Boehm (with typed GC and Parallel Mark)
nathan@ubuntu:~$

So now we just need to configure Apache. The install process copied a mod_mono.conf to the directory: /etc/apache2.  You’ll need to enable this by moving it to /etc/apache2/mods-available and creating a link to that file at /etc/apache2/mods-enabled.

cd /etc/apache2
sudo mv mod_mono.conf mods-avail*
sudo ln -s /etc/apache2/mods-available/mod_mono.conf /etc/apache2/mods-enabled/mono.conf

#optionally restart apache server. more changes coming
sudo service apache2 restart

Configure Website

We’re using Mod_Mono to handle Asp.Net requests with Apache. I’ve mentioned before that I’m a big fan of the Mono website’s Mod_Mono configuration tool. We can use that tool to build our initial VirtualHost configuration. Then change the MonoServerPath to be the one we installed at: “/opt/mono-2.8/bin/mod-mono-server4”  When you’re done, upload (or move) this folder to your home directory on the server.

NOTE: We’re using mod-mono-server4 for Asp.Net 4.0 runtime. You can use mod-mono-server2 for 2.0-3.5 Asp.Net and mod-mono-server for 1.0-1.1 Asp.Net.

NOTE: If you’re unfamiliar with copying files from your Windows box to a Linux one, you can use FileZilla with an SSH (SFTP) connection. Connect to something like: “sftp://username@host” then treat it like any other FTP connection.

Here we’ll setup our web folders, permissions, move our configuration file, link it, and restart the web server. Our generated configuration file is named ubuntu.conf and was uploaded to my home folder.

sudo mkdir /srv/www
sudo mkdir /srv/www/ubuntu
sudo chown root:www-data /srv/www/ubuntu -R
sudo chmod 775 /srv/www/ubuntu -R
mv ~/ubuntu.conf /etc/apache2/sites-available
cd /etc/apache2/sites-en*
sudo ln -s ../sites-available/ubuntu.conf "000-ubuntu.conf"
sudo service apache2 restart

NOTE: I prefixed the link name with “000” since Apache loads configuration files in alphabetical order. It’s not necessary for this scenario, but if you’re running multiple virtual hosts and want a “default”, this is good to know. Make your default VirtualHost load first.

You might also want to give yourself permissions to write to the new web directories for publishing sites. The easy way to do this (maybe not best practice), would be to add yourself to the www-data group used by apache & mono, which we just setup with full access.

sudo usermod -a -G www-data your_username

Later when we upload the site, this will be a factor. The alternative will be to upload your published site to your home directory and then with an ssh console, sudo mv the published files to the web directories if you choose not to add yourself to the www-data group.

For this sample, we used all the default parameters in our configuration. Take note that debugging is enabled. I also left IO Mapping enabled to allow Mono to treat file system paths as case insensitive. You can improve performance by disabling IO Mapping. The VirtualHost configuration looks like this:

<VirtualHost *:80>
  ServerName ubuntu
  ServerAdmin web-admin@ubuntu
  DocumentRoot /srv/www/ubuntu
  # MonoServerPath can be changed to specify which version of ASP.NET is hosted
  # mod-mono-server1 = ASP.NET 1.1 / mod-mono-server2 = ASP.NET 2.0
  # For SUSE Linux Enterprise Mono Extension, uncomment the line below:
  # MonoServerPath ubuntu "/opt/novell/mono/bin/mod-mono-server2"
  # For Mono on openSUSE, uncomment the line below instead:
  MonoServerPath ubuntu "/opt/mono-2.8/bin/mod-mono-server4"

  # To obtain line numbers in stack traces you need to do two things:
  # 1) Enable Debug code generation in your page by using the Debug="true"
  #    page directive, or by setting <compilation debug="true" /> in the
  #    application's Web.config
  # 2) Uncomment the MonoDebug true directive below to enable mod_mono debugging
  MonoDebug ubuntu true

  # The MONO_IOMAP environment variable can be configured to provide platform abstraction
  # for file access in Linux.  Valid values for MONO_IOMAP are:
  #    case
  #    drive
  #    all
  # Uncomment the line below to alter file access behavior for the configured application
  MonoSetEnv ubuntu MONO_IOMAP=all;LD_LIBRARY_PATH=/opt/mono-2.8/lib:$LD_LIBRARY_PATH;PATH=/opt/mono-2.8/bin:$PATH
  #
  # Additional environtment variables can be set for this server instance using
  # the MonoSetEnv directive.  MonoSetEnv takes a string of 'name=value' pairs
  # separated by semicolons.  For instance, to enable platform abstraction *and*
  # use Mono's old regular expression interpreter (which is slower, but has a
  # shorter setup time), uncomment the line below instead:
  # MonoSetEnv ubuntu MONO_IOMAP=all;MONO_OLD_RX=1

  MonoApplications ubuntu "/:/srv/www/ubuntu"
  <Location "/">
    Allow from all
    Order allow,deny
    MonoSetServerAlias ubuntu
    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>

Create and Publish Asp.Net MVC2 Application

In Visual Studio 2010, select the File menu –> New –> Project. In the new project dialog near the top center, select the .NET Framework 4.  Then on the left, select Web (under C#), and choose ASP.NET MVC2 Web Application.  There are a few key items we’ll need to remove to make this compatible with Mono.

First, open the ~/Models/AccountModels.cs file and remove all data annotations attributes from the three model classes’ properties. You may leave “DisplayName”. I’ve found (without investing a lot of time in this), that the data annotations doesn’t seem to work out of the box. Removing these attributes will allow it to run properly under Mono. Keep in mind, this also means, you’ll need to write your own server-side validation. It’s not too painful; we’ve been doing this for  years anyway.

Finally, build and test-run the site from visual studio. It should work fine with the built-in Casini test web server. If all is well, right click on the project (in solution explorer) and Publish the site. Publish it to the file system and choose a destination folder. You don’t need to include the App_Data folder, and you can delete all files before publish if you want.

Upload the published files to the server using FileZilla, and copy them to /srv/www/ubuntu.  Apache doesn’t need to be restarted when you update web files and assemblies. You should now be able to browse the site at http://your_test_server_host/.  All should work except membership since we haven’t configured the database yet.

Setup Membership with MySql

Awhile back, I wrote a post dedicated to MySql Membership with a simple config generation tool do this for you. Checkout the post for more details after setting up your database server. Setting up membership is identical between Asp.Net MVC and web forms. Install and configure MySql Server first. Then setup a placeholder database for the membership data. The first time you use membership during runtime will automatically generate the database schema.

Install MySql and Setup Empty Membership Database

sudo apt-get install mysql-server

NOTE: The default install will lock it down to localhost access only, which is good for a server. But for test, if you want to access it from your machine, you’ll have to tell it to bind to a LAN address (instead of 127.0.0.1). Take a peek at /etc/msyql/my.cnf file to update this setting. The comments describe the change.

I’m giving application user full access (including schema change privileges) to the membership database. MySql Memebrship provider updates its own schema as you update the provider.  Checkout the MySql docs if you want to limit account privileges.

nathan@ubuntu:~$ mysql -h localhost -u root -p
mysql: create database membership;
mysql: grant all privileges on membership.* to 'aspnet_user'@'localhost' identified by 'secret_password';
mysql: quit

Configure Membership

I used my configuration tool and generated a simple membership config.  Copy the membership sections to your into the “system.web” section of your root web.config and setup a connection string with the same name as the one used in membership. (“Default” is used here).

Next, if you’re using a factory default version of MySql Connector/NET, you’ll need to download its source and recompile it with .NET 4.0 profile. I found while doing this that the published 2.0 version seemed to blow up when referencing transaction methods. I found that it was a known bug and should be resolved in upcoming versions of the connector. For now, you’ll need to recompile MySql.Web and MySql.Data with a 4.0 profile if you want it to work under Mono with membership.  The sample version packaged here has that done already.

NOTE: The version of MySql .NET Connector I was using at the time I wrote this tool (6.3.5) didn’t support hashed passwords with Mono runtime. I made a minor tweak to this version that will disable the Mono runtime check for hashed passwords and will allow it (since it does work in the current version of Mono). 

<authentication mode="Forms">
    <forms
      loginUrl="~/Account/Logon"
      timeout="30"
      name="6ad58f32-93d5-463f-9d99-835942aca8f5"
      path="/"
      requireSSL="false"
      slidingExpiration="true"
      defaultUrl="Default.aspx"
      enableCrossAppRedirects="false"/>
</authentication>

<membership defaultProvider="MySqlMembershipProvider">
    <providers>
        <clear/>
        <add name="MySqlMembershipProvider"
              type="MySql.Web.Security.MySQLMembershipProvider, mysql.web"
                connectionStringName="Default"
                enablePasswordRetrieval="false"
                enablePasswordReset="true"
                requiresQuestionAndAnswer="false"
                requiresUniqueEmail="true"
                passwordFormat="hashed"
                maxInvalidPasswordAttempts="5"
                minRequiredPasswordLength="6"
                minRequiredNonalphanumericCharacters="0"
                passwordAttemptWindow="10"
                applicationName="/"
                autogenerateschema="true"/>
    </providers>
</membership>

<roleManager enabled="true" defaultProvider="MySqlRoleProvider">
    <providers>
        <clear />
        <add connectionStringName="Default"
            applicationName="/"
            name="MySqlRoleProvider"
            type="MySql.Web.Security.MySQLRoleProvider, mysql.web"
            autogenerateschema="true"/>
    </providers>
</roleManager>

<profile>
    <providers>
        <clear/>
        <add type="MySql.Web.Security.MySqlProfileProvider, mysql.web"
              name="MySqlProfileProvider"
              applicationName="/"
              connectionStringName="Default"
              autogenerateschema="true"/>
    </providers>
</profile>

Also for Mono, I added the DbProviderFactories section for MySql data in case it wasn’t already setup. Insert this adjacent to the <system.web> section.

<system.data>
    <DbProviderFactories>
        <clear/>
        <add name="MySQL Data Provider"
            description="ADO.Net driver for MySQL"
            invariant="MySql.Data.MySqlClient"
            type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data"/>
    </DbProviderFactories>
</system.data>

Once updated, you should now be able to run the MVC app and register/authenticate user accounts. If you have any problems, double-check your data source value, username and password. Make sure you can connect to it with a mysql client and your app credentials.  Also I find the Asp.Net Configuration Tool built-in to Visual Studio helpful when testing Membership configuration. It will show you a number of users and roles if membership is configured properly.

Sample

Grab the sample from here or github. Includes: Web App, dependencies, & virtual host config. Comments, enhancements, pull requests, are welcome!

Wrap-Up

So now we’re done. The next thing you should checkout is how to use inversion of control with MVC2. I’ve been writing applications lately using SubSonic3 (repository mode) and Unity Application Block 2.0 for dependency injection. Coupled with MvcContrib test helpers and Rhino Mocks, this is a powerful combination for writing rock solid, testable applications that run on Windows AND Mono.

Here are a few useful links for this post:

• Install script for Mono 2.8 on Ubuntu
• Install script for Mono 2.8 on Fedora
• Sample application built here. Includes: Web App, dependencies, & virtual host config.
• MySql .NET Connectors w/ Data Provider and Membership Provider
• MySql membership configuration generation tool