There have been some changes to the packaging in 2.4.2 to make doing this much easier
Previously, there were two mod-monos:
mono-apache-server for ASP.NET 1.1
and
mono-apache-server2 for ASP.NET 2.0
The blocker on autohosting has been that mod_mono's autohosting is hard-coded to use "mono-apache-server"
As of Karmic (soon), this has been changed - we now have:
mono-apache-server1 for ASP.NET 1.1
mono-apache-server2 for ASP.NET 2.0
mono-apache-server as a symlink either settable by the user, or by default, pointing to mono-apache-server2
I haven't enacted the change in packaging to make mod_mono_auto the default, but now at least, it works with asp.net 2.0 - and depending on how well it works, I may make auto the default in future.
There have been some changes to the packaging in 2.4.2 to make doing this much easier
Previously, there were two mod-monos:
mono-apache-server for ASP.NET 1.1
and
mono-apache-server2 for ASP.NET 2.0
The blocker on autohosting has been that mod_mono's autohosting is hard-coded to use "mono-apache- server"
As of Karmic (soon), this has been changed - we now have:
mono-apache-server1 for ASP.NET 1.1
mono-apache-server2 for ASP.NET 2.0
mono-apache-server as a symlink either settable by the user, or by default, pointing to mono-apache-server2
I haven't enacted the change in packaging to make mod_mono_auto the default, but now at least, it works with asp.net 2.0 - and depending on how well it works, I may make auto the default in future.