Hi David, No, that's not enough simply to remove an app's files; it will still be listed in the app manager, and in the package manager, as being installed. I think the answer would be what you seem to be suggesting: WE needs the ability to call some uninstall routine registered by the app, at the time WE is uninstalling the app. Chip
_____ From: David [mailto:eleph...@tele2.no] Sent: Wednesday, May 23, 2012 10:34 PM To: gw-scripting@gwmicro.com Subject: Uninstalling an app? Let's say, you have an app, named MyApp. By standard, a WE app has four files. That is, MyApp.ini MyApp.vbs MyApp.wepm MyAp.xml . OK, I know, there is a built-in package remover in WE. But many apps do have a number of other files attached to them. Either files that are shipping in the package - and who I guess, the package remover takes care of. Or, it could be files that are generated "on the fly", when the app is running. In the latter case, the package remover will not take care of all the extra files. I wonder if the app itself, has an uninstall feature inside its code. The first thing the app would do, is to remove all its self-produced extra files. But then, the user would have to manually activate the package remover in WE. This leads me to my actual question here. If I let the app delete its four "basic" files - that is, .ini, .vbs, .wepm and .xml - will that be enough to have it removed from WE. Or, is there another suggested way of having an all-automated "self-removing" feature built into my app? Thanks for all ideas.
