This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Prevent Downgrade of Non-versioned Files
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 16, 2008
11:45 AM
Prevent Downgrade of Non-versioned Files
In a merge module, we have a number of files which by nature are not versioned - xml files, text files, jar files. Is there a common mechanism that can be used to prevent downgrade of these files?
The only work around that I've found so far is to set the REINSTALLMODE property to "p" on the command line. It would be nice, however, to have an automated way.
Thanks.
Scott
The only work around that I've found so far is to set the REINSTALLMODE property to "p" on the command line. It would be nice, however, to have an automated way.
Thanks.
Scott
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 17, 2008
10:00 AM
Companion files
Stefan Krueger
InstallSite.org
InstallSite.org
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 18, 2008
01:11 PM
Thanks for the reply. I've seen the companion files feature. I think it will work well for text files, but not for jar files. Jar files are essentially libraries that by nature have their own version. However, they don't use the standard Windows file versioning mechanism.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 26, 2008
09:12 AM
A "dummy" DLL included just for file versioning purpose could make companion files work in this case. It's the best solution I can think of right now.
Stefan Krueger
InstallSite.org
InstallSite.org