Sep 30, 2022
12:50 PM
We understand and support the update process for replacing shared files such as DLLs in the Windows folder, but for files in our INSTALLDIR, we always want to replace them.
We run into problems when users modify some of those data files which end up with Modified Dates later than what we're trying to install. If we have Always Overwrite checked for those files in our build, our update works fine.
The problem is that we sometimes forget to set that when we update our InstallShield file configurations (e.g. we choose the same file names from another folder). They default to NOT overwrite.
Is there a way to always overwrite all files in a folder and/or a programmatic way to verify all the files in a folder are set to Overwrite so we don't make a setup build that omits that?
Thanks.
... View more
Labels
- Labels:
-
InstallShield
-
InstallShield 2022
Jun 16, 2022
03:09 PM
What I've since discovered with this solution is that the registry branch (key) defined with a variable doesn't get removed when the program is uninstalled. It is set to uninstall the entire key.
Any reason why it would be different as a variable versus hardcoded value?
... View more
Jun 15, 2022
04:28 PM
I'm trying to figure out the same problem.
After the "This setup will perform an upgrade..." message, if there isn't a specific event for it, is there something one can add to the OnBegin event to tell it's trying to perform an update?
We need to distinguish this from an attempt to uninstall.
... View more
Apr 15, 2022
01:28 PM
I encountered this too for a setup that was previously working. Not sure what "The string contains a character not in the 7 bit ASCII character set." means. The files didn't change. Started signing 218B.tmp ...
Number of errors: 1
SignTool Error: ISignedCode::Sign returned error: 0x80092022
The string contains a character not in the 7 bit ASCII character set.
SignTool Error: An error occurred while attempting to sign: 218B.tmp I could digitally sign the setup.exe file afterwards using a DOS command line. Not sure why InstallShield stopped doing so. It's still able to digitally sign other builds.
... View more
Mar 25, 2021
04:30 PM
When the setup program runs and detects an upgrade situation, the user is prompted that an upgrade will occur. That's nice but we want to verify the user is entitled to the upgrade (in case they already returned it for a refund). We have routines that authenticate the user (same as when they install for the first time), but do not know where to put that code for an update. I also can't seem to debug it. It just shows the prompt and starts updating it. Is there an Event that's triggered when it goes into update mode? It's also odd that sometimes the prompt appears to update, while other times, it just goes to the Modify/Repair/Remove screen. Is there an event to capture their selection after that? We want to validate them for modify and repair, but want everyone to be able to Remove it.
... View more
Labels
- Labels:
-
InstallShield
Mar 11, 2021
03:59 PM
I need the setup program to have Administrator privileges to install some DLLs, however, it should only be installed for one user, not the whole machine. If I don't require administrator, everything installs in the right user location, user registry, and shortcut menus appear for the user. If I require administrator execution level for the setup, when the user runs it, it prompts for the administrator login as expected. However, it installs everything for the "Administrator" rather than the user, so everything is private and fine for the Administrator but isn't available for the original user. That is, if the Administrator logs in, it shows up on the Start menu, the files are visible, etc. When the user logs in, nothing is available. What am I doing wrong or does a setup which requires Administrator login automatically become available to everyone who logs into that PC such that it's really installed on the Local Machine? Thanks in advance for your help and insight.
... View more
Labels
- Labels:
-
InstallShield
Sep 27, 2018
12:17 AM
I'm not sure what a "Basic" MSI project is. I use an ISM file and it has the OnFirstUIBefore event. I've read and re-read the "What is a major upgrade?" section and still can't seem to get it to work. When I keep the same Upgrade Code and change the Product Code, the installation runs, but it installs but doesn't uninstall the previous version. If I keep the same Product Code, it triggers the Error 1316 I mentioned earlier. Are there any sample ISM files I can use to see how it works? I'm stuck with a situation where the existing Product Configuration already has a product and upgrade GUID that I presume overrides the values at the General Information level. So when I'm setting those values, I'm doing it at the Product Configuration, not overall General Information section. Should I change something at that level? Thanks in advance for your patience with me.
... View more
Sep 26, 2018
09:38 AM
This is an MSI project. It installs a Windows program. I created a new build with a different product code but same Upgrade Code as the previous installation. For whatever reason, the Upgrade Code GUID was already defined for the version we've already released. When the setup program ran, it treated it like a new product rather than trying to upgrade it.
... View more
Sep 25, 2018
01:05 PM
Thanks. Sorry for not picking up on that. We'll go ahead and try that. How about running the OnFirstUIBefore function during the Major Upgrade?
... View more
Sep 24, 2018
07:00 PM
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.
... View more
Sep 24, 2018
03:07 PM
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-exists 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?
... View more
Sep 24, 2018
01:36 PM
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.
... View more
Sep 22, 2018
05:09 PM
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?
... View more
Sep 21, 2018
02:09 PM
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. .
... View more
Labels
- Labels:
-
InstallShield 2016
Sep 10, 2018
09:11 AM
Yes, that's the same experience we have. We have not figured out how to avoid it. Our only solution is to not launch the program after installation which is obviously very inconvenient. I wonder how others get around this or if there's something we're doing wrong with our configuration to not have everything installed at that point.
... View more
Latest posts by DataAnalyzer
Subject | Views | Posted |
---|---|---|
213 | Sep 30, 2022 12:50 PM | |
250 | Jun 16, 2022 03:09 PM | |
382 | Jun 15, 2022 04:28 PM | |
288 | Apr 15, 2022 01:28 PM | |
298 | Mar 25, 2021 04:30 PM | |
309 | Mar 11, 2021 03:59 PM | |
3207 | Sep 27, 2018 12:17 AM | |
3207 | Sep 26, 2018 09:38 AM | |
3207 | Sep 25, 2018 01:05 PM | |
4375 | Sep 24, 2018 07:00 PM |
Activity Feed
- Posted Setting Always Overwrite for our files in INSTALLDIR on InstallShield Forum. Sep 30, 2022 12:50 PM
- Posted Re: Registry Branch Defined in Code on InstallShield Forum. Jun 16, 2022 03:09 PM
- Posted Re: Catch upgrade in installscript? on InstallShield Forum. Jun 15, 2022 04:28 PM
- Kudoed Re: Catch upgrade in installscript? for epotter. Jun 15, 2022 04:26 PM
- Posted Re: SignTool Error on InstallShield Forum. Apr 15, 2022 01:28 PM
- Posted For Upgrade, Need to Verify the User is Still Valid; Can't Debug on InstallShield Forum. Mar 25, 2021 04:30 PM
- Tagged For Upgrade, Need to Verify the User is Still Valid; Can't Debug on InstallShield Forum. Mar 25, 2021 04:30 PM
- Tagged For Upgrade, Need to Verify the User is Still Valid; Can't Debug on InstallShield Forum. Mar 25, 2021 04:30 PM
- Posted How can I require Administrator and still install for the user? on InstallShield Forum. Mar 11, 2021 03:59 PM
- Tagged How can I require Administrator and still install for the user? on InstallShield Forum. Mar 11, 2021 03:59 PM
- Tagged How can I require Administrator and still install for the user? on InstallShield Forum. Mar 11, 2021 03:59 PM
- Posted Re: Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 27, 2018 12:17 AM
- Posted Re: Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 26, 2018 09:38 AM
- Posted Re: Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 25, 2018 01:05 PM
- Posted Re: Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 24, 2018 07:00 PM
- Posted Re: Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 24, 2018 03:07 PM
- Posted Re: Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 24, 2018 01:36 PM
- Posted Re: Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 22, 2018 05:09 PM
- Posted Upgrading a Product with a New Product Name Fails on InstallShield Forum. Sep 21, 2018 02:09 PM
- Posted Re: OnFirstUIAfter Program Launch Triggers ActiveX component can't create object (429) on InstallShield Forum. Sep 10, 2018 09:11 AM