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
- :
- Minor Upgrade Problems
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
‎Apr 13, 2009
02:14 PM
Minor Upgrade Problems
Project Type: Basic MSI
I've been trying to create a minor upgrade for some time now and I can't seem to make it work properly. I create a package with version 8.0.0.22 of our software. I can install it and run it just fine. I replace three DLLs with the 8.0.0.25 versions of the files and update the ProductVersion property to 8.0.0.25. I create a minor upgrade item and point it to the previously created 8.0.0.22 setup. When I create the new package I see a warning claiming "The CreateFolder table contains new content". This appears to be false. The CreateFolder table has no content whatsoever.
Also, I don't seem to be able to apply the upgrade I created. The 8.0.0.22 package installs correctly and the software functions. When I attempt to apply the 8.0.0.22->8.0.0.25 upgrade the installer runs in maintenance (Mondify/Repair/Remove) mode. I have run through this installer just to see what happened and the three DLLs appear to be upgraded (right-click, properties, version) but upon launching the software I see the attached dialog box. The software has yet to launch after applying this upgrade, even if I select "Run Setup" and point to the setup.exe or setup.msi.
Clearly I am doing something wrong with creating this minor upgrade. Can someone give me some pointers on what I need to do to create a minor upgrade? I've read over so many documents (even the Learning MSI Projects book from Acresso) and still do not have a functioning upgrade. Thanks for any help any of you can give.
I've been trying to create a minor upgrade for some time now and I can't seem to make it work properly. I create a package with version 8.0.0.22 of our software. I can install it and run it just fine. I replace three DLLs with the 8.0.0.25 versions of the files and update the ProductVersion property to 8.0.0.25. I create a minor upgrade item and point it to the previously created 8.0.0.22 setup. When I create the new package I see a warning claiming "The CreateFolder table contains new content". This appears to be false. The CreateFolder table has no content whatsoever.
Also, I don't seem to be able to apply the upgrade I created. The 8.0.0.22 package installs correctly and the software functions. When I attempt to apply the 8.0.0.22->8.0.0.25 upgrade the installer runs in maintenance (Mondify/Repair/Remove) mode. I have run through this installer just to see what happened and the three DLLs appear to be upgraded (right-click, properties, version) but upon launching the software I see the attached dialog box. The software has yet to launch after applying this upgrade, even if I select "Run Setup" and point to the setup.exe or setup.msi.
Clearly I am doing something wrong with creating this minor upgrade. Can someone give me some pointers on what I need to do to create a minor upgrade? I've read over so many documents (even the Learning MSI Projects book from Acresso) and still do not have a functioning upgrade. Thanks for any help any of you can give.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 13, 2009
02:23 PM
Windows Installer uses only 3 fields for versioning: aaa.bbb.cccc
If you add a fourth field, it just gets ignored. Try versioning your setups 8.0.22 and 8.0.25.
If you add a fourth field, it just gets ignored. Try versioning your setups 8.0.22 and 8.0.25.
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 13, 2009
04:31 PM
While a Minor Upgrade technically requires that you change one of the first three recognized digits of the ProductVersion property, it's not the reason you're seeing this issue.
Windows Installer enters Maintenance mode as opposed to upgrade mode when the PackageCode of the installation performing the upgrade matches the installation currently on the machine. Because the PackageCode represents a specific structure and build of the MSI package in question, MSI defines both as being the exact same.
What you would want to do is ensure in the Product Configuration for your Release that you have the "Generate New Package Code" option set to "Yes", or that you generate a new PackageCode for your product in the same view. Doing this will assist in moving you forward with the issue you're encountering.
Windows Installer enters Maintenance mode as opposed to upgrade mode when the PackageCode of the installation performing the upgrade matches the installation currently on the machine. Because the PackageCode represents a specific structure and build of the MSI package in question, MSI defines both as being the exact same.
What you would want to do is ensure in the Product Configuration for your Release that you have the "Generate New Package Code" option set to "Yes", or that you generate a new PackageCode for your product in the same view. Doing this will assist in moving you forward with the issue you're encountering.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 13, 2009
05:54 PM
douglasm wrote:
Windows Installer uses only 3 fields for versioning: aaa.bbb.cccc
If you add a fourth field, it just gets ignored. Try versioning your setups 8.0.22 and 8.0.25.
Thanks. This appears to have been the problem for the upgrades not working. Both installers appear to run correctly and the application runs accordingly, now, as well.
However, I still have the same problem with the CreateFolder warnings. How does one go about correcting this type of problem? I don't know where to look for these component codes. There are twelve of these "Val0010" warnings yet only three DLL files (thus three components) were changed for the minor upgrade. These three components have only a single file in each of them. How can I possibly have twelve differences when only three files have changed?
Val0010: The data in component '_8EED4496082ABC8DC1D35EED2B610D98' differs from the previous setup. However, this component will not reinstall in an upgrade scenario. Therefore, the changes will not be applied to the target system during the upgrade. Table: 'CreateFolder' Record: '_9FA393DA8F34495D87472B2FD6F562B9;_8EED4496082ABC8DC1D35EED2B610D98'
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 13, 2009
05:59 PM
bryanwolf wrote:
While a Minor Upgrade technically requires that you change one of the first three recognized digits of the ProductVersion property, it's not the reason you're seeing this issue.
Windows Installer enters Maintenance mode as opposed to upgrade mode when the PackageCode of the installation performing the upgrade matches the installation currently on the machine. Because the PackageCode represents a specific structure and build of the MSI package in question, MSI defines both as being the exact same.
What you would want to do is ensure in the Product Configuration for your Release that you have the "Generate New Package Code" option set to "Yes", or that you generate a new PackageCode for your product in the same view. Doing this will assist in moving you forward with the issue you're encountering.
The "Generate New Package Code" is and has always been set to "Yes". The "Package Code" field is empty.