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: Upgrade does not copy new 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
‎May 04, 2011
10:06 AM
Upgrade does not copy new files
Hi together!
We want to publish an upgrade of one of our products. Therefore, we changed the Product Version and the Package Code. All files which have to be updated do have a higher file version. This procedure works fine for some versions of our product.
But now, it does not work. Like all the times before, the installer asked whether I want to upgrade product xyz or not. Thats ok and the known behavior. After clicking "yes", the installer runs but copies no files. Instead, after the installation has been finished, I try to start the product with the appropriate shortcut on the desktop. The installer runs again. In the details of the shortcut, there is the info, that the application will be installed on first start. And that is, what the installer does. Further, after clicking the product shortcut, the installer can not find the MSI package anymore.
Can somebody help me please? what is the reason for this? One thing to mention: we migrated from InstallShield 2010 to 2011 with that product.
Thanks a lot for fast help!
Best regards!
Robin
We want to publish an upgrade of one of our products. Therefore, we changed the Product Version and the Package Code. All files which have to be updated do have a higher file version. This procedure works fine for some versions of our product.
But now, it does not work. Like all the times before, the installer asked whether I want to upgrade product xyz or not. Thats ok and the known behavior. After clicking "yes", the installer runs but copies no files. Instead, after the installation has been finished, I try to start the product with the appropriate shortcut on the desktop. The installer runs again. In the details of the shortcut, there is the info, that the application will be installed on first start. And that is, what the installer does. Further, after clicking the product shortcut, the installer can not find the MSI package anymore.
Can somebody help me please? what is the reason for this? One thing to mention: we migrated from InstallShield 2010 to 2011 with that product.
Thanks a lot for fast help!
Best regards!
Robin
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 06, 2011
07:32 AM
I also migrated many products to 2011 but didn't face such issue. Can you check if the target folder is Read-Only? If yes, we need to modify its properties.
I am assuming you didn't change the Upgrade Code.
Regards,
Robins
I am assuming you didn't change the Upgrade Code.
Regards,
Robins
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 09, 2011
06:19 AM
Hi.
I might be able to give you a clue what is going on.
As far as I remember does a already installed feature not trigger a copy of new files to the target machine. In other words, If you are making a update dont just make a component for a new file and then add the component to a feature. You have to create a new Sub feature of the already installed one, and make it depending on the already installed feature.
When the upgrade runs, the new feature (New file) will be installed because it depends on the top feature.
This is my first answer to other people problems, Im not a IS shark but I hope it did make sence.
Best regards,
Jens
I might be able to give you a clue what is going on.
As far as I remember does a already installed feature not trigger a copy of new files to the target machine. In other words, If you are making a update dont just make a component for a new file and then add the component to a feature. You have to create a new Sub feature of the already installed one, and make it depending on the already installed feature.
When the upgrade runs, the new feature (New file) will be installed because it depends on the top feature.
This is my first answer to other people problems, Im not a IS shark but I hope it did make sence.
Best regards,
Jens