Hello,
for one of our customer we must include some configuration files in our setup and after setup process our applications are modifing these files.
How can I keep this CHANGED files after uninstallation? New files still exist, but changed files are gone.
Thanks
Heiko
How to avoid uninstall of changed files
-
- Posts: 252
- Joined: Sat Dec 03, 2011 3:07 am
- Location: Konstanz, Germany
- Contact:
How to avoid uninstall of changed files
Kind regards
Heiko Kummerfeld
MIK GmbH
Setup developer for .NET BI Software (12 products)
Head of quality assurance
technical consultant
Heiko Kummerfeld
MIK GmbH
Setup developer for .NET BI Software (12 products)
Head of quality assurance
technical consultant
-
- Site Admin
- Posts: 5360
- Joined: Sun Aug 22, 2010 4:28 am
Re: How to avoid uninstall of changed files
Dear Heiko,
to keep such files just don't include them with the MSI database. In this way those files will be not removed on un-install.
In other words, you may use a similar approach just after Apply Install;
Hope this helps you.
Regards
to keep such files just don't include them with the MSI database. In this way those files will be not removed on un-install.
In other words, you may use a similar approach just after Apply Install;
Code: Select all
....
Apply Install (get result into variable SUCCESS)
if Variable SUCCESS Equals COMPLETE
Set Variable NATIVE_ENGINE to TRUE
Install Files <my File path> to $TARGETDIR$
Set Variable NATIVE_ENGINE to FALSE
end
...
Hope this helps you.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Who is online
Users browsing this forum: Google [Bot] and 50 guests