Group: Forum Members
Posts: 538,
Visits: 2.2K
|
The way install (and uninstall) paths are usually handled is that your program creates an entry in the WIndows registry where it stores all its needed path information. There could be many more paths you might want to remember, e.g., a "temp" directory or a charts and map directory, etc. When your program is installed, it makes a note of these paths in the registry. Your program then gratiously gives the user the last word on where to install itself. The uninstall process is then also a simple matter.
The way updates are currently handled is also pretty cumbersome. I have to manually uninstall the old version and then do a fresh install on the new version. Why not have the installer of the new version check in the registry where the old one resides, uninstall it automatically, and then proceed with the install of the new version? This would be much more user friendly and oflload your support staff. It would also make it a simply process to let the user decide freely where s/he wants the program to reside.
Rigidly deciding where the program has to be put is neither user friendly nor elegant from a programming point of view.
Regards, -- Chris.
|