cancel
Showing results for 
Search instead for 
Did you mean: 
DataAnalyzer
Pilgrim

Upgrading a Product with a New Product Name Fails

We have a product "MyProduct Basic" that people install.

We create updates for the product and just change the version number in InstallShield, When the setup program is run, if it detects it's installed, it upgrades it. If not, it performs the full installation. Works great!

We created a new Product Configuration with a new name (e.g MyProduct Pro). We want that setup to be similar to the upgrade and the Basic version if it's already installed. Because the product name changed, that doesn't happen even though I have it using the same product GUID (or not). Neither works..

Is there a way to update the existing installation and change the name so it replaces the existing program on disk and in the Windows Control Panel Add/Remove Programs list?

Without that, we are forced to tell the user:

1. Uninstall the existing version and install the new one, or
2. Have our setup program keep the old program name (so Basic stays forever) which would confuse people if they go to the control panel list since the thought they own the Pro version. For new installations, it would say Basic when it should be Pro, so that's unacceptable.

Not sure what I'm missing to handle this. Thanks in advance.
.
Labels (1)
0 Kudos
15 Replies
Dan_Galender
Occasional contributor

Re: Upgrading a Product with a New Product Name Fails

To change the product name, you'll want to create a Major Upgrade. Change the ProductName, change the ProductCode, change the ProductVersion, and author a Major Upgrade item in the Upgrades view.
0 Kudos
DataAnalyzer
Pilgrim

Re: Upgrading a Product with a New Product Name Fails

DanGalender wrote:
To change the product name, you'll want to create a Major Upgrade. Change the ProductName, change the ProductCode, change the ProductVersion, and author a Major Upgrade item in the Upgrades view.


Thanks. Glad to know it's possible. I must be misunderstanding something.

Where is the Major Upgrade Item? Is it under the Product Configuration or Releases? How do I link the two Product Configurations to each other?
0 Kudos
Dan_Galender
Occasional contributor

Re: Upgrading a Product with a New Product Name Fails

Look in the Upgrades view (Between Path Variables and Releases) and read the topic "What is a Major Upgrade?"

If both versions were created by the same project, the linkage is done through the Upgrade Code.
0 Kudos
DataAnalyzer
Pilgrim

Re: Upgrading a Product with a New Product Name Fails

Thanks. I see the Upgrade code in the Media/Upgrades section.

How is that different from the Upgrade Code in the Releases?

Is there only one Upgrade code for all Releases or do I use the same Product Code and Upgrade Codes in the Releases (General tab) to tie them together?

And if so, does it need to be the same Upgrade Code as the one in the Upgrades page.

Thanks.
0 Kudos
Dan_Galender
Occasional contributor

Re: Upgrading a Product with a New Product Name Fails

If you don't change it (and you shouldn't), The UpgradeCode will remain the same across all releases and versions of your projects. You use it in the Major Upgrade field so that the upgrade process can find older versions of your product that have been installed on a given machine when installing this version.
0 Kudos
DataAnalyzer
Pilgrim

Re: Upgrading a Product with a New Product Name Fails

Thank you. I've confirmed that we can get the setup to kick into upgrade mode by using the Upgrade Code, but it triggers an Error 1316: The specified account already exists.
Seems like I ran into this error 3 years ago when I tried this and discovered it was tied to changing the product name: https://community.flexerasoftware.com/showthread.php?219059-Error-1316-The-specified-account-already...

Not sure how to get around since we need to change the product name.

That said, maybe this other issue can fix that. When a Major Upgrade occurs, we need to run the code we currently have in the OnFirstUIBefore function. We have code to prompt the user to enter their new Serial Number that we need to validate for the upgrade. That function is skipped during an update. Can we set something so that it's run only for new installations and Major Upgrades?
0 Kudos
Dan_Galender
Occasional contributor

Re: Upgrading a Product with a New Product Name Fails

Did you change the ProductCode in the project when you changed the product's name?
0 Kudos
DataAnalyzer
Pilgrim

Re: Upgrading a Product with a New Product Name Fails

The product configuration has a Product Code GUID for the new release that is the same as the Product Code for the previous version. But the names are different.
0 Kudos
Highlighted
Dan_Galender
Occasional contributor

Re: Upgrading a Product with a New Product Name Fails

Please read that topic I referred you to "What is a major upgrade?" in the Upgrades view. The first sentence under the heading "How do you get a major upgrade to work?" states that the ProductCode must be changed for a major upgrade to work (emphasis mine). Changing the product's name is permitted in a major upgrade, but not necessary. Changing the ProductCode is necessary.
0 Kudos