[Mono-dev] upgrading an app

[Tom Bombadil]

Ok Sounds good. I was trying to avoid restarting the app manually, to
avoid the downtime, but I guess this is the safest thing to do.

Thanks Hubert and Miguel for your replies!

Cheers ;)



Hubert FONGARNAND wrote:
> Le vendredi 15 septembre 2006 à 14:28 -0700, Tom Bombadil a écrit :
>> Hi all...
>>
>> We are running into a few problems with a mod_mono/asp.net app (no dlls,
>> nor assemblies, yet) in two different servers using the same NFS
>> volume... If we use server A to update the files in the NFS volume,
>> server B's app will fail.
> 
> I use NFS too, in order to share .net webapps!
> asp.net use inotify or gamin to be aware of changes... and those methods
> doesn't works with NFS...
> 
>>
>> The doc below says that mono picks up changes in the src automatically:
>> http://www.mono-project.com/FAQ:_ASP.NET#My_application_fails_if_I_replace_binaries
>>
>> My question is: how does mono pick up changes in the src files, when we
>> replace them? by the date in the file? by md5 checksum?
>>
>> Also, if we are using a DLL with mod_mono... what's the best way of
>> reloading it:
>> - "rm + cp" as shown in the URL above; or
>> - just move the file over, and use the control panel, as shown here:
>> http://www.mono-project.com/Mod_mono#Control_panel
> When i update an app... i always restart them manually!
> 
>>
>> And if you dont mind my curiosity, why do we have delete the DLL?
>>
>> Thanks a lot ;)
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com <mailto:Mono-devel-list at lists.ximian.com>
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> _______________________________________________
> Ce message et les �ventuels documents joints peuvent contenir des
> informations confidentielles.
> Au cas o� il ne vous serait pas destin�, nous vous remercions de bien
> vouloir le supprimer et en aviser imm�diatement l'exp�diteur. Toute
> utilisation de ce message non conforme � sa destination, toute diffusion
> ou publication, totale ou partielle et quel qu'en soit le moyen est
> formellement interdite.
> Les communications sur internet n'�tant pas s�curis�es, l'int�grit� de
> ce message n'est pas assur�e et la soci�t� �mettrice ne peut �tre tenue
> pour responsable de son contenu.