gigi wrote:Hi,
Please give me more details about this, what is the organization of your application? What exactly do those updates and how do you create them?
Regards,
Gigi
_________________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
Thanks for your reply.
Our clients already have our application loaded using an Installshield project. I am now using Advanced installer for updates to the program. I plan to use AI to roll out updates of our software from this point forward. The install project only contains executables used by our software, and ocx and dlls required for our software. All these files will already exist from the installshield project.
I have created a professional project type. It is a project that simply copies the new executables and dll's to the install directory for the program which already exists. The files are stored in the project in a CAB file. It does write specific entries to the registry when auto-registering an ocx or dll, but does not write any other properties (such as icons on the desktop or start menu). I have not modified settings from the project creation, so it should be pretty bone stock.
It is a very basic project I am using for GPO rollout, but when I uninstall the MSI, it deletes all the files originally installed by the MSI. This leaves the program useless.
Basically, I would like to make my updates work the same as any update from any third party vendor. If I decide that the update causes more issues than it's worth, I would like to uninstall it and roll back to a previous version of the code.
Is this possible? Is there a way to tell the AI project to backup the previous files and restore them if the MSI is un-installed?
Thanks.
Bill.