mod_mono is not going to work like this

[vulcan_@…]

just did the port upgrade apache2 reviewing the /opt/local/conf dir for any changes i saw that mod_mon.conf was present, but not used in the httpd.conf.

I went looking for info on how to complete the install as apache could not serve a .aspx file succesfully.

I see some .. mistakes? .. in the instructions to complete the installation manually

post-install {
26	        ui_msg ""
27	        ui_msg "To finish the configuration of this Apache module, you must add"
28	        ui_msg "the following (modulo site variations) to your httpd.conf file:"
29	        ui_msg ""
30	        ui_msg "AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config .ascx"
31	        ui_msg "LoadModule mono_module libexec/httpd/mod_mono.so"
32	        ui_msg "MonoUnixSocket /tmp/mod_mono_server"
33	        ui_msg {Alias /mono "/usr/share/doc/xsp/test"}
34	        ui_msg ""
35	        ui_msg "Then do the following:"
36	        ui_msg ""
37	        ui_msg "cd ${prefix}/share/doc/xsp/test"
38	        ui_msg "mono ${prefix}/bin/mod-mono-server.exe --root . --applications /mono:."
39	        ui_msg ""
40	        ui_msg "Finally, restart apache (if running) and point a browser at:"
41	        ui_msg "http://127.0.0.1/mono/index.aspx to test ASP page-serving ability"
42	        ui_msg ""
43	}

1. there is no xsp directory under share/doc
2. reading about the xsp port i see it is "a small web server that hosts the Mono System.Web classes". It is not a dependency, and i do not want it anyway .. i want mono to work with my apache2 server.
3. The xsp test code should be copied to the mono port so that there is a .Net test available without needing xsp to be installed first.
4. the .exe extension on the executable name tells me this was a cut-paste job from a Windows install page.
5. just figured out that the Alias definition inside {} is actually needed in the httpd conf file so that the URL in the Point a Browser At .. step works. This info should be mentioned so that people know this URL is only for testing the installation. Maybe change the Alias name to "mod_mono_test" so that the URL is the more obvious "mod_mono_test/index.aspx" ?

so .. any suggestions on how i should really install and test mono would be great .. i will be fooling around with it so if i get anything that i can propose to improve the port i will.

[vulcan_@…]

oops .. messed up the wiki formatted list. try again

1. there is no xsp directory under share/doc
2. reading about the xsp port i see it is "a small web server that hosts the Mono System.Web classes". It is not a dependency, and i do not want it anyway .. i want mono to work with my apache2 server.
3. The xsp test code should be copied to the mono port so that there is a .Net test available without needing xsp to be installed first.
4. the .exe extension on the executable name tells me this was a cut-paste job from a Windows install page.
5. just figured out that the Alias definition inside {} is actually needed in the httpd conf file so that the URL in the Point a Browser At .. step works. This info should be mentioned so that people know this URL is only for testing the installation. Maybe change the Alias name to "mod_mono_test" so that the URL is the more obvious "mod_mono_test/index.aspx" ?

[vulcan_@…]

update to point 5. after reading the man pages for mono and mo-mono-server

The combination of the Alias definition and the --root argument to the server executable mean that all .Net pages have to be installed under share/doc/xsp/test, which is not what is wanted generally.

i don't yet know what to suggest as an improvement .. perhaps after i play with it some more.