Well,

I couldn't get the Post Processor to work using a windows service.  Time
was tight so I ended up using a scheduled console app.

My problem was:

Three windows services:
Service A - does some work
Service B - does some work
Service C - is the updater

When Service C identifies that a new version of one of the worker
services is available it downloads it into a download folder.  The Post
Processor then stops the relevant service, copies in the new code, and
then restarts the service.

This seems to work fine the first time.  However the Updater service
seems to keep a handle on the file that it has originally downloaded and
never lets go.  So when another version becomes available it downloads
ok but the version that it copies into the new directory is the first
version!  And therefore it also executes the Post Processor from the
first version.

If you found a way around this I would appreciate it if you could
enlighten me.  You originally mentioned using a differnet App Domain but
I can't seem to find a way to do that either.

regards,