• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 744
  • Last Modified:

InstallShield product and update codes

I thought I knew the answer to this but just can't get it to work properly...

I had an installation procedure created within Visual Studio 2010 but decided to re-write it using InstallShield 2010 as I don't like the interface to the VS solution.

I have copied over the Product and Upgrade codes from the Visual Studio Installer and have set the same product name.  When I run the installation built in InstallShield I correctly get an error saying that the product is already installed - just what I wanted.

I now change the version number in InstallShield and re-generate the PRODUCT CODE.  rebuild the installation and run it again.  What happens is that I get both the old and new versions of my application installed.  I expected the old version to be upgraded as the UPGRADE CODE is the same in both installations.

Any thoughts on what I am missing?  I need my new Installation to perform an upgrade
0
ChrisMDrew
Asked:
ChrisMDrew
  • 4
  • 3
1 Solution
 
Vadim RappCommented:
Does the table UPGRADE have the entry with this upgrade code that includes the old version? what does it have in the column "Attributes"?
0
 
ChrisMDrewAuthor Commented:
Sorry - which table do you mean?  Need a bit more information as to how to debug this before I go back and just use the VS2010 installer project!
0
 
Vadim RappCommented:
Table Upgrade. I'm not sure if you see it in the version of Installshield that comes with Visual Studio, but here's what it looks like in the "full" version. screenshot
If you don't see it, you can open the MSI with Orca and check.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Vadim RappCommented:
...btw, setups created by VS "traditional" s&d project have been quite robust. My personal interest at looking at what exactly Installshield offered stopped at realizing that in order to actually have it, I have to go and register with Installshield. Previously, similar things were run with Obfuscator, as I recall, and maybe something else. I think it's not very ethical to sell the product bundled with de-facto shareware, trialware, etc.
0
 
ChrisMDrewAuthor Commented:
O think my problem is down to a mis-understanding of how InstallShield handles these codes.  Looking at the 'Properties' within InstallShield I have

Product Code - the documentation suggests that you change this for each upgrade of a product

UpgradeCode - the documentation suggests that this must always be the same for every version of a product

Package Code - no idea what this is - seems to mirror the product code in that the documentation suggests that it needs to change for each release.

I have previously used the VS s&d projects but I am not keen on the way in which files are added.  I like the idea in InstallShield of including a folder and automatically all files and folders within that folder are included.  I have an 'Upgrade' folder which includes database upgrade files - a new folder is created for each update.  In VS I have to remember to add all files necessary which is easy to forget when you have have just added a new file.
0
 
Vadim RappCommented:
re. package code, here's the explanation: http://blogs.msdn.com/b/pusu/archive/2009/06/10/understanding-msi.aspx . I don't fully understand myself why it's necessary, but that's the way it is. Maybe there were some historical reasons.

In both VS S&D and in all installation-authoring tools integrated with VS, the concept used for adding the files is "primary output". VS usually includes in it the executable it has built, plus you can mark other files. Installshield's wildcard-based inclusion has resulted in numerous installations coming with all sorts of temporary files, log files, etc. If you install a product, and find some $$$ files it installed, you know it has been created by Installshield. The real fun begins if the application itself removes any of these files - then on the next launch the user is presented with self-repair of the product, to restore the $$$ file.
0
 
ChrisMDrewAuthor Commented:
Thanks - decoded to stay with VS S&D after all - seems much easier!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now