On Wed, 2005-03-23 at 22:25 -0700, Jesse Pasichnyk wrote: > Iâm experience a problem with mod_mono (1.0.6), and Iâm running the > 1.1.4 framework.
> The issue is that Iâll start up apache with: MonoRunXSP True > First of all, with this release I actually get a mod-mono-server.exe > spooled up for each virtual host I have setup as a MonoApplication, > which was not happening before off the bat. Now the issue is that if > I rebuild/update a site, I have to actually restart apache for this to > go into effect, otherwise it keeps pulling up my previous copy of the > site. mod-mono-server.exe shuts down the application domain running your asp.net application and starts a new one when it detects that a change has been made. The problem is that the runtime still has the "old" assemblies loaded and returns those instead of loading the new ones. There's already a bug report for that. > Do I need to turn off MonoRunXSP? Or is there something else going on > here. If I need to turn it off, when should this be used. If you don't want to stop/start apache, you can run mod-mono-server.exe by yourself (use the same arguments as mod_mono uses when spawning those). In this case, whenever you update your application you can run mod-mono-server --terminate and then start it over again. -Gonzalo _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
