I have a product, lets call it Bob V1.0, when its uninstalled it removes all its files correctly. Unfortunately we forgot to mark a couple of components as "permanent" so its removing files we would like it to leave behind in the My Documents folder.
I've already fixed this for our new V2.0 release. The problem however is during an upgrade from V1.0 to V2.0 MSI uninstalls V1.0 for us, deleting these files.
I need some way to prevent this or fix it. I cant update or change the V1.0 installer, its too late for that, but I was wondering if there is something I can do in the V2.0 installer prior to it removing V1.0 to effectively remove the problematic components from the MSI database, leaving the files behind, that way when V1.0 is uninstalled it will not know to delete the My Documents files.
My only other option is to copy the files and restore them after the V1.0 removal and I'm worried about all the corner cases of that script (different users doing V2.0 install to the V1.0 etc.) and would like to avoid it.
Any help is greatly appreciated, this has become a bit of a hot issue for me.
FOLLOW US
Get the latest news in Application Packaging