Chris Aitken wrote:
Hi All,

I feel the documentation regarding mod_mono/AutoConfiguration could do with
a little more work to make it clear.
  
Agreed.  (If there is no objections I'm going to start to rewrite that page along with the mod_mono page.)  Should a bug be filed and attach a diff or other means?
The Autoconfiguration page claims:
"For those of you that have an existing configuration, you'll have to enable
the feature by adding

        MonoAutoApplication enabled"

Here is my stanza:

    MonoRunXSP True
    MonoPath "/opt/mono"
    MonoApplications default "/ASPNET:/var/www/ASPNET"
    MonoDocumentRootDir "/var/www/ASPNET"
    MonoExecutablePath "/opt/mono/bin/mono"
    MonoServerPath "/opt/mono/lib/xsp/1.0/mod-mono-server.exe"
    AddHandler mono aspx ashx asmx ascx asax config ascx

So I have added "MonoAutoApplication enabled" to the stanza, and whilst the
original files still work, any new application deployed does not work.
Obvoiously something else has to be changed, but what?

I was also led to believe (from the mod_mono page) that all the MonoRunXSP
crap etc was ot required anymore. Application fails when removed.
  
Questions)

Are you trying to do vhosts?

Can you send an example of how you are changing things once you add more than one application?

What do you mean by application fails when removed?

Exactly what version of Mono/mod_mono are you running?

>From my understanding, someone correct me if I'm wrong, MonoAutoApplication replaced the need to put MonoApplications or AddMonoApplication lines in your config file.

If you could try to comment out those lines and see if that helps. You may also want to test with and without the "default" process for MonoApplications. (MonoApplications default)

I hope this is helpful.

Cheers,

C.
_______________________________________________
Mono-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to