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
- :
- JS files not getting upgraded which are Dynamically linked using IS2015
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
‎Mar 04, 2016
07:33 AM
JS files not getting upgraded which are Dynamically linked using IS2015
Hi,
We have created Installscript MSI project and we added .js files using Dynamic file Linking .
We installed the setup (1.0.0.0) in one of our system, after installation we manually change one .js file(say Detailsone.js file) in installed directory. Now we created setup 1.2.0.0 and upgraded the latest setup(1.2.0.0)in that machine, we can notice that Detailsone.js file is not getting replaced/overwritten by the latest Detailsone.js file .
Can you please suggest why it is not getting replaced on upgrade when we manually change the .js file ?
Thanks in advance
We have created Installscript MSI project and we added .js files using Dynamic file Linking .
We installed the setup (1.0.0.0) in one of our system, after installation we manually change one .js file(say Detailsone.js file) in installed directory. Now we created setup 1.2.0.0 and upgraded the latest setup(1.2.0.0)in that machine, we can notice that Detailsone.js file is not getting replaced/overwritten by the latest Detailsone.js file .
Can you please suggest why it is not getting replaced on upgrade when we manually change the .js file ?
Thanks in advance
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 10, 2016
09:31 AM
sureshkottakki,
I don't know if there is a correct way to do it using InstallScript MSI, but we have never gotten a web application to upgrade properly using minor upgrades with that project type. We had to convert all of ours to InstallScript Only projects where you can use the Component setting "Overwrite" and set it to "Always".
HTH
I don't know if there is a correct way to do it using InstallScript MSI, but we have never gotten a web application to upgrade properly using minor upgrades with that project type. We had to convert all of ours to InstallScript Only projects where you can use the Component setting "Overwrite" and set it to "Always".
HTH
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 15, 2016
05:02 AM
But we are supposed to use Installscript MSI project only, any suggestions ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 15, 2016
07:13 AM
Somehow InstallShield must be recognizing that it did not put that file there, so it is not removing/replacing it. If that file is commonly replaced you could try using a custom action to delete that file early in your upgrade process... then the installer will add the new file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 29, 2016
09:07 AM
Hi rguggisberg,
Thanks for the suggestion , I created the Custom action which will call the .dll function to delete the files in the folder, I am able to delete the files through that custom action but it is not keeping any files in the particular folder after successful upgrade. Can u please suggest after which sequence I should call this custom action?
Thanks for the suggestion , I created the Custom action which will call the .dll function to delete the files in the folder, I am able to delete the files through that custom action but it is not keeping any files in the particular folder after successful upgrade. Can u please suggest after which sequence I should call this custom action?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 29, 2016
05:03 PM
I would try right after RemoveFiles in the 'Install Execute' sequence.
You probably want to use 'Deferred Execution in System Context'.
If you continue to have trouble put MessageBoxes at the start and end of your CA. Then you can look to verify that only the files you expect are in the folder when you enter the CA; that the files are gone as expected when the CA finishes; and that the new files are populated after that.
You probably want to use 'Deferred Execution in System Context'.
If you continue to have trouble put MessageBoxes at the start and end of your CA. Then you can look to verify that only the files you expect are in the folder when you enter the CA; that the files are gone as expected when the CA finishes; and that the new files are populated after that.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)