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
- :
- Config File not replacing while upgrade
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
Nov 06, 2015
06:49 AM
Config File not replacing while upgrade
Hi ,
We have created a Installscript MSI project, the version of the setup is 1.0.1.0 and it has two dlls with version 1.0.1.0 and a config file.
Now we made some content changes to that config file and build that setup with version 1.0.2.0 and the dlls versioned to 1.0.2.0, but nothing we changed to the functionality related to these dlls.
Now while upgrading from 1.0.1.0 to 1.0.2.0 the config file is not replacing while upgradation, we can see the old stuff in that config file even the dlls got replaced .
Can anyone tell me why the config file is not getting upgraded? And what we need to do to replace the config file while upgradation.
Regards,
K V Suresh
We have created a Installscript MSI project, the version of the setup is 1.0.1.0 and it has two dlls with version 1.0.1.0 and a config file.
Now we made some content changes to that config file and build that setup with version 1.0.2.0 and the dlls versioned to 1.0.2.0, but nothing we changed to the functionality related to these dlls.
Now while upgrading from 1.0.1.0 to 1.0.2.0 the config file is not replacing while upgradation, we can see the old stuff in that config file even the dlls got replaced .
Can anyone tell me why the config file is not getting upgraded? And what we need to do to replace the config file while upgradation.
Regards,
K V Suresh
1 Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 18, 2015
04:24 AM
It may be because your config file has a newer date than the one in the msi. If that is the case it will not be replaced, unless you have file versioning on your config file.
