ssrikant
07-18-2003, 01:32 PM
Hey friends,
I need suggestion to go about making an uninstaller ...
BTw how could i detect current instances of my application are running or not..if running a mesg box saying that shut the instances and resume uninstaller...
-s
1. How you will make uninstaller probably depends on the installer. There are two ways: have names of the sections installed in the registry and then uninstall them (like my setup program does), or have a LOG file with entries for each item installed. That way you can loop through it backwards and uninstall items.
2. I can only point you - try to use EnumWindows
Bobo the Thief
07-18-2003, 02:23 PM
There's also an easy way to see whether another instance of your application is running. The PrevInstance property of the App object.
As for the uninstaller ... is usually created by the packager. Why don't you use Package & Deplayment Wizard?
ssrikant
07-18-2003, 03:08 PM
There's also an easy way to see whether another instance of your application is running. The PrevInstance property of the App object.
As for the uninstaller ... is usually created by the packager. Why don't you use Package & Deplayment Wizard?
Thanks for answering....
val:
I liked the concept of writing all the installed components in into install.log but if a case arises that u happen to delete the install.log file and then there is no way to get that uninstaller to work ..which to my understanding would read the content of the file and delete the path specified by it ...and there by looses its purpose..but that could be avoided by locking the install.log which cannot be delected (by some means ) ..any insights in this aspect
Bodo:
although i like to use package wizard but i was not able to customize it for my specific needs ..
-s
Bobo the Thief
07-18-2003, 03:19 PM
Well, professional installers don't deal with this aspect ... once you delete their log file they're useless.
You could place the file in the windows directory (that's also pretty common), where only novice users wanting a handicaped operating system would attempt a cleanup.
But the most professional solution to hiding the log would be using the system registry (although if you have a huge program with hundreads of files, filling the registry with them wouldn't be too professional any more...). So keep the log file - encript it if you don't want it to be readable.
I would recommend to create a directory in C:\Program Files\Your Installer\InstallationID where you will place all files required to run your setup. Then set folder's attribute to hidden. As far as I know, InstallShield works like that.
ssrikant
07-18-2003, 06:03 PM
I would recommend to create a directory in C:\Program Files\Your Installer\InstallationID where you will place all files required to run your setup. Then set folder's attribute to hidden. As far as I know, InstallShield works like that.
Thanks ..that explains it all..
i try that ..
cheers
-s