David,

Thanks for the explanation, it's very helpful.

Now, let me describe, that we currently have (I don't think, we're going to change it):

All applications (we didn't compile an exe, we compile with app extension) reside on the server. The main application is called JobControl. User enters into the system and then he/she invokes and closes applications. Until he/she invokes an application A, I can recompile it on the server without problem. But if it was once invoked, then closed, I can not recompile it anymore, until users completely get out of the whole system. As I said, all applications use common classlibraries. I think, then application is closed, it didn't properly close referenced classlibs, so they're still in the memory. That's the reason, I can not recompile an application, even if nobody uses it at this time.

My question is: is it possible make a proper cleanup and allow to recompile application, after this application was closed, but the main system is still running? If not, we have to finally implement a launcher approach (using any of already available launcher classes in Download section).

Thanks again for your help.

>Nadya,
>
>While an EXE is running there is a file level lock on the file which will prevent it from being written to by a build or copy.
>
>The users should copy the exe from the network drive to their local machines. You can build directly to the network exe or to your local drive and then copy it to the network server.
>
>If the users are all running the exe from the server you will have to kick them all out when you need to update the exe. Your launcher program can check the local and server exe version stamps to know if it needs to update the users machine.
>
>>Do you mean, applications should be always copied to local's machines of the users or I have to use my own local drive, re-compile projects, when update them on the server? Is it possible at all to have all applications running directly from the server (our current situation)?