>But what do you mean by that, exactly? Are you referring to a loader that checks the local copy against the network copy and brings down the network copy if it is newer, then starts the local copy? I've never been fond of that technique, though I'm not saying it's bad or anything. Most of my apps are not near the 22 MB. That one is just because it uses the very bloated CodeBook framework. It's normally between 4 MB and 10 MB and people haven't complained about load times. I'm not opposed to the type of loader you mention - if I correctly assumed what you meant - and might use it if needed, but just haven't seen the need.
>

I use a loader that does exactly that. The EXE's on the network have unique names - this makes it easy to upload new builds w/o any concurrency problems. Users run the latest build, and only pull one across the network if it is newer.