I am hoping somebody might be able to help me with this. I am strugging with my Advanced Installer project, trying to get it to ignore the application folder of the previous version of my application, and force it to install into a new folder. However, no matter what I do it insists on defaulting to install in the previous version's folder. Is there any way to prevent this, short of ignoring the [APPDIR] altogether and hard-coding the installation folder path?
To elaborate:
* The previous version of my product installed to [ProgramFilesFolder][Manufacturer]\[ProductName]\, and lets say it was called 'product 2.0'
* The new version is called 'product 2.1' and I want it to remove 2.0, but install itself into [ProgramFilesFolder][Manufacturer]\product 2.1\
I have tried:
* Just changing the Product Name
* replacing [ProductName] in the application folder path with a hard-coded 'product 2.1'
* changing the application path to [ProgramFilesFolder][Manufacturer]\ and hard-coding a 'product 2.1' folder in the 'files and folders'
but no matter what I do, I can't seem to get around the logic that picks up the previous version's install folder as a default.
I can't let the users install into that folder, because there are certain configuration files left behind by the uninstall that are incompatible and would cause the new version to crash. I don't want to remove those files, because I want the user to have the option of rolling back to the old version, and retaining that configuration information. I don't want to go the 'side by side install' route, because that will just lead to confusion and users running the wrong version.
So, any suggestions?
Thanks!
P.S. I tried searching for previous posts on this topic, but all the relevant keywords like "upgrade", "install" and "location" get rejected as being too common; so my apologies if this has been answered previously!
FOLLOW US
Get the latest news in Application Packaging