I try the apps, and keep going back to yours because I like it a little better, and each time I enter more data. Or consider the case where I install your application in the process of evaluating several. And probably not to buy you a cup of coffee. If your uninstall killed all of the work I’d already done, I might be tempted to come looking for you. I for one would be very unhappy if I installed an application, entered a lot of data, and then decided to use something else instead that would read that data from your app. You can’t use InnoSetup to uninstall anything it didn’t install, and you shouldn’t want to do so. NOTE: Don’t be tempted to use a wildcard here to delete all files in It should present all the possible options in a nice GUI and generate the script for you.Įdit: An example from the Inno Setup documentation: īut they strongly you don’t do something like That being said, I don’t know offhand what the script is, but if you use ISTool (highly recommend) just got to the Uninstall Delete section and add things you want removed. The reasoning is that what if for whatever reason the user decided to put their own files in your installation directory that they didn’t want removed, or saved data that they might want to keep around (maybe they uninstall is to install a newer version?) I think the recommended approach is to specify what to remove in the uninstall section. In this case your patch_manifest.txt would not only include the relative path to the file but also the MD5 checksum. Take the case of a user who accidentally installed your application to C:\Windows\ or C:\Program Files.Īnother good idea is to verify that the file is in fact “your file” by performing an MD5 check prior to deleting it. Uninstaller’s have elevated privileges which could potentially destroy a user’s computer. It is very important that you do not delete by wildcard (. Make this part of your build process so you don’t forget to update it! Your application should be shipped with a patch_manifest and the patch_manifest should be updated with every patch. All files within a directory should first be listed followed by the directory – directories which are not empty cannot be delete. Note: The order of the lines in the patch_manifest is important. New files can be added to the disk in this manner which are not a part of the uninstaller.įor this case I suggest that you create a “patch manifest” file which keeps a running record of what files should be in the ') '\' itemsToDelete Īnd a sample of the patch_manifest.txt data/something_here.dat One of these cases is when you have an application that updates itself when it is started. There are cases to want to delete files which were not initially written to the user’s disk at time of installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |