[Mono-list] Xcopy deployment of dlls

Chris Aitken chris@ion-dreams.com
Thu, 27 Jan 2005 10:58:11 -0000


> On Thu, 2005-01-27 at 09:30, Chris Aitken wrote:
> > > > Is mono supposed to support xcopy deployment?
> > > 
> > > Yes.
> > > 
> > > > I have to restart xsp (actually apache2 with mod_mono)
> > > everytime I add
> > > > a new dll to my ./bin/ directory.
> > > 
> > > That's not XCOPY Deployment, at least as I understand it.
> > >
> > > XCOPY deployment is the ability to run an application
> > > *without* running an installer first.  Thus the application is 
> > > location-independent, and deploying (installing) to 
> another machine 
> > > is as simple as copying the application.
> > > 
> > > What you want is the ability for xsp to restart the AppDomain 
> > > whenever it notices that a DLL has changed within the bin 
> directory.  
> > > Last I knew, this wasn't entirely functional as the 
> > > FileSystemWatcher wasn't entirely functional.
> > 
> > So what you're saying is "Mono is supposed to support xcopy 
> > deployment, but currently doesn't"?
> > 
> 
> I think what he is saying is that mono *does* support Xcopy 
> deployment but what you are asking about is something else 
> that doesn't work properly at the moment.  Although I am not 
> quite sure what the problem with FileSystemWatcher is as I 
> have been using it for quite some time now.

Having reviewed my config files, I now have xcopy deployment up & running (I
thought I had seen it working before).

Now I feel stupid - still, its something I'll look out for again!

Thanks All

Chris


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.