Because I can't recompile when a user is running the application. There are many users and I can't ask them to exit the application every time I make a minor change. (And I don't want to come in early or stay late to do it.)

It's extrememly unusual, and I'd say inadvisable, for the production users to be using the of the executable directly produced by your compile. Most developers develop on one machine, or at least in a different folder, and then copy new versions of the executable to a different machine, or to a different folder where the user's actually access it. If you did it that way, then you could compile any time you want, making your life a lot easier, and copy the resultant exe to the production folder when the users aren't around. If you need to do that via a schedule, then you can write and schedule a batch file to handle it.

0

MariaHaltAuthor Commented: 2004-09-09

I actually do that. The problem is my personal schedule. The user's are in it a lot longer than I am available to recompile or copy a file, I need to do when I positively know that a user is not going to be running it, like the middle of the night. Thanks for your input.