We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

scottharner
Posts: 2
Joined: Mon Oct 15, 2012 1:50 pm

Maintining Data Files On Upgrade

Is there a way to tell advanced installer not to over-write a data file if it already exists during an upgrade? If so, what version of advanced installer is required for this? What version would be required to copy a data file from a previous installation to a different location?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Maintining Data Files On Upgrade

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

In order to achieve what you want you can take a look on our "Prevent Repair or Uninstall" article. Also, please keep in mind that our "Persistent user data" feature is available only in a "Professional" or above license.
What version would be required to copy a data file from a previous installation to a different location?
I'm afraid I don't fully understand what you mean. Can you give us more details about your scenario (maybe exemplify)?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
scottharner
Posts: 2
Joined: Mon Oct 15, 2012 1:50 pm

Re: Maintining Data Files On Upgrade

Thanks. You have answered my question reasonably well enough. I'm using Advanced Installer for a freeware/open source project because I don't have money for a full version of Visual Studio and did not want to use Click Once. Of course, since I don't even have money for Visual Studio, I additionally don't have money to pay for the professional version of Advanced Installer. As they say, beggars can't be choosers, so I will try to employ a different strategy whereby my application takes on some of the logic that I was originally expecting the installer to take on.

Return to “Building Installers”