I'm setting up a installation (.exe) for Office Plugin and using Installshield limited edition. I have old version 1.0 was distributed and used by end-user, right now I would like to redistribute new version 2.0, and would like to make program to remove or override completely old version when install new version.
I tried "upgrade path" to change product code but it seem does not override completely old version.
Does anyone can help or let me know there is any way to do that?
Thank you!
Ok, I got solution now. Beside change Product Code & Product version I have to change INSTALLDIR path to resolve it.
Step to do it:
Step 1: From installshield => Select upgrade path => add new => Browse to old version (.exe), to get Upgrade Code. If the app support multi-language with multiple install file (.exe) version we need to add all these old version in upgrade path
Step 2: From installshield go to "General Information Tab" to check make sure Upgrade Code is the same, then change product code and Product Version
Step 3: From installshield go to "General Information Tab" to change INSTALLDIR path for new version, for example from MyApp1.0 to MyApp2.0
Related
I need to find an older version of Advanced Installer - specifically v12.7.2 - I know this is really old - for reasons out of my control this is the version I have to use. Could anyone point me where to download this installer? The website is up to v18 and I can't find anywhere there to get older versions.
Link of the company website https://www.advancedinstaller.com/download.html
If you have a license key, enter it here: https://www.advancedinstaller.com/customer-information.html
Otherwise, you can contact the company and they may be able to find it for you.
I have an app that uses a VS 2015 installer project.
Our BONEHEAD vendor, ComponentOne, released a new version of several assemblies upon which my product depends.
Here's the rub:
Old DLL version: 4.1.20102...
New DLL Version: 4.0.20162...
The newer DLL at least have newer file dates than the older one.
Of course, the newer DLL fix real user problems brought about by the bugs in the C1 components since corrected.
While I can get to the correct DLL by having the end user fully uninstall the older version of my product and installing the newer version, this is unworkable because:
We have an auto-update function that phones home and checks for the latest patch and installs it to update prevoius version; and
Our customers are female, 60+ and cyberphobic.
The project already has the RemovePreviousVersions property set to true, and I was hoping that this did a complete uninstall silently. It does not; the six assemblies with the version error are not replaced. The DetectNewerInstalledVersion property is also set to true; I tried to install with False, and it has no effect.
I also tried to explicitly include all detected dependencies of the C1 assemblies and it has no effect.
Is there a way to force the install project to overwrite the assemblies as long as the file date is newer regardless of the wrongly-encoded version?
Edited to add the following:
I tried making a custom action to delete the offending assemblies before installing anything - it runs after the files are installed. :(
I tried InstallShield LE, only to find out that it could not discover the dependencies more than one level deep, and provided no convenient way to explicitly specify the dependencies. I also could find nothing that would let me say to overwrite the assemblies based on date or unconditionally.
Thanks for any help you can offer!
I found an effective workaround.
I already had RemovePreviousVersions set to true, so I changed the application's default folder by adding [ProductVersion] onto the end of the path.
What this accomplished was:
It deleted the old assemblies; and
It created the new assemblies in the new folder.
This solved the problem nicely. No setting REINSTALLMODE to amus; no brute force solutions.
Lets say my current production version is 1.2.3 and the new product version is 1.2.3.4.
Now, during installation, it will throw a warning message saying something like "The setup has detected the version 1.02.003 of...... already installed. This setup updates ..... to the same version that is already installed, therefore this update is not needed. Do you want to install the update anyway? "
This will be very misleading. Does anybody know a solution for this?
It is not InstallShield, but rather Windows Installer, the underlying technology has the behavior you observe. Take a look at this article, which explains how Windows Installer treats versioning.
The important part for your case is this:
Note that Windows Installer uses only the first three fields of the
product version. If you include a fourth field in your product
version, the installer ignores the fourth field.
This explains why it considers the new one to be the same version. So, the suggestion is either change the third digit, or go with small updates instead. Here is how you can apply small updates by re-installing the product.
I have a problem with my installJammer project. Currently am creating a setup for a java application.
I need to create an action that is invoked when the user selects to upgrade to the new version. To be more clear, a window with two radio buttons (Update and Upgrade) appear if a previous version exists.
When the user clicks upgrade, the existing version is to be upgraded with the existing. How can I do this?
Expecting any one's help as I need the solution ASAP.
Thanks in advance.
Dear friend,
In installjammer, An upgrade installer is one that skips some of the procedures of
a regular installer and adds its information to the uninstall of the previously-installed
application. you can upgrade your project by using upgrade application ID can be accessed by using the <%UpgradeApplicationID%> virtual text.
By setting the <%UpgradeApplicationID%> you can update your exciting project with current. for the suitable effect,you should set an upgrade application pan in installjammer.after that,set the actions that is - check for previous install,get previous install info.then you should set a virtual text action for perfect upgradation.in virtual test action, check the advance properties,mark the auto update as "Yes",then fill the virtual text as <%UpgradeApplicationID%>. after that furnish the message box,exit etc.as your requirement wishes. hop you will get this. if any more confusions, please refer installjammer user guide by downloading the following link - www.installjammer.com/docs/InstallJammerUserGuide.pdf
I am releasing a new version of my product (minor upgrade), which I'm planning to package as a patch. This is a Basic MSI project in InstallShield 2009.
The installer creates some shortcuts on the desktop and in the All Program menu, this shortcuts make a reference to the version number, e. gr. "My Product 7.3", "My Product 7.3.2".
The change in the name of the shortcut is causing that after the upgrade is finished, the system ends up with duplicated shortcuts, one for version 7.3 and a second for version 7.3.2.
I made some research on this and started using the RemoveFile table, this worked fine when I created my patch 7.3.1, but now in patch 7.3.2 it isn't working in some cases. Let me clarify this.
This scenario DOES work:
I install my product version 7.3 (full installer)
Run patch 7.3.1 (windows installer patch). Shortcut for 7.3 is deleted fine.
Run patch 7.3.2 (windows installer patch). Shortcut for 7.3.1 is deleted fine.
This scenario does NOT work:
I install my product version 7.3
(full installer)
Run patch 7.3.2
(windows installer patch). Shortcut
for 7.3 is NOT deleted.
Note: I have tested my 7.3.2 version by running the full installer instead of the patch, and it works fine. It performs the minor upgrade and removes the old shortcut.
In my 7.3.2 patch I've added both 7.3 and 7.3.1 as previous setups.
A verbose log doesn't seem to provide much information (or probably I'm not doing the right search).
The component associated to the records in the RemoveFile table is updated correctly which I can verify in the log:
MSI (s) (58:EC) [15:51:44:846]: Component: ProgramFiles; Installed: Local; Request: Local; Action: Local
I will appreciate any help that you may provide.
Thanks.
Juan Carlos
Check the patch installation works, if only 7.3 is inclided in previous setups.
Seems like the problem in this case was related to the fact that when I accidentally changed the source files when creating the patch. So the file table didn't match with the files that I was really shipping. This created some sort of conflict with the upgrade. I've repeated the scenario using always the correct files and it worked fine.