>I'm working on a project where the client will want to make future updates available to users from the web. With the way the software will be distributed initially, I should be able to count on the fact that all necessary runtime files have already been loaded on the users machine, & I'm thinking future updates via download should be a no brainer. Is there anything else I need to consider now, to make future download releases/updates simple?

For our applications here we have developed a web install for the whole Naval Base. Once installed the exe checks for any updates when it starts (updates like a new EXE build). If it detects one it informs the user that an update is available and sends them to the web page that instructs them on how to install the new version (also the exe closes, as we dont let them run an old version if a new one is available). The web page has information on what the new version number is and any enhancements, bug (heaven forbid) fixes, or System Improvement Requests that have been incorporated in this release. All our data is also out on our intranet available for downloading by those who wish to have the data locally versus running a stand alone exe with network data. So far after the initial web install, the users have not complained about any version updates we have implemented. So far the only complaint I have received is the fact the new versions always want the user to reboot their machine, I have not quite figured out why, but I tell them to do so just to be on the safe side.