I´m having some sort of dilemma which I don't know how to resolve.
My installer creates some database files on installation, actually the application does.
I was able to do allot of stuff with AI but im quite lost with this which is not something very complex either.
When I upgrade the application, the old database files get renamed to .old and the new ones are installed which makes appear the software installed a new, and user loses his settings. If you actually to in there and manually delete the files and rename back the .old to the correct extensions it works.
There seems to be way to persist users data. One is to mark this files as persistent, but even in the AI tutorials this is not recommended, as when you uninstall them they would not get erased, not a big deal either and the only one if the one that points out to script here:
http://www.advancedinstaller.com/user-g ... le-ca.html
Except that this is ratter referred to install, not sure if that would work on upgrades. Still that sounds very complex. Would not be easier to mark files not to be overwritten on upgrades? I see this options for folders but not for individual files or have them back renamed?
FOLLOW US
Get the latest news in Application Packaging