>I have the same here - one exe constantly scanning a file for other exes to run and checking for a newer version. It works a treat and there is no real work involved as almost everything is automated.

I think I may take this technique a step further. My "base" executable contains most of the functions common to all the applications. The applications themselves "sit" on top of the base. This allows me to mark the shared modules as excluded in the applications, and they're dynamically linked to the ones in the base program. Really helps reduce the size of the modules, plus if a change ever occurs in the base program, only it has to be recompiled and distributed.

The only real drawback that I know of is that dynamic linking is somewhat slower. However, I've been using this technique successfully since FPD 2.0, and have found the performance acceptable.