PDA

View Full Version : Remove previous setup before install new setup



ratul_pramanick
11-08-2010, 08:46 AM
Please help how can I create a setup using Install shield Premier so that following requirement can be full fill:

If I have already installed a setup of my .Net application.When I try to install new version of the same application then older one should uninstall first and installed new version . I am trying to create a setup using "Basic MSI project".

So please guide me the process.

ratul_pramanick
11-10-2010, 01:14 AM
I am new to installshield. Please help me , this is very urgent. If I install new version that detect older one and wants to update . But after installation no changes are reflected. Please help me out from this problem.

gale.wang
11-10-2010, 01:25 AM
I am new to installshield. Please help me , this is very urgent. If I install new version that detect older one and wants to update . But after installation no changes are reflected. Please help me out from this problem.

Are you sure you have updated registry for the new version?

ksyadav1980
11-10-2010, 04:16 AM
You need to do MAJOR UPGRADE.
Search in Installshield 2010 help for it.

Major Upgrades

A major upgrade is a comprehensive update of a product that needs a change of the ProductCode Property.

A typical major upgrade removes a previous version of an application and installs a new version. A major upgrade can reorganize the feature component tree. For more information, see ProductCode and Changing the Product Code.


During a major upgrade using Windows Installer, the installer searches the user's computer for applications that are related to the pending upgrade, and when it detects one, it retrieves the version of the installed application from the system registry. The installer then uses information in the upgrade database to determine whether to upgrade the installed application.

To enable the installer upgrade capabilities, each package should have an UpgradeCode Property and an Upgrade Table. Each stand-alone product or product suite should have its own UpgradeCode. For more information about using the UpgradeCode see the section Using an UpgradeCode. Each record in the Upgrade table gives a combination of the upgrade code, product version, and language information used to identify a set of products affected by the upgrade. When the FindRelatedProducts Action detects that an affected product is installed on the system, it appends the product code to a property in the ActionProperty column of the Upgrade table. The RemoveExistingProducts action and the MigrateFeatureStates Action remove or migrate the products listed in the ActionProperty list. Package authors can also follow the procedure described in the topic: Preparing an Application for Future Major Upgrades.

Windows Installer upgrade packages can be authored such that major upgrades will not install if the user already has a newer version of the application installed. For more information about how to author a package that will not install over a newer version, see Preventing an Old Package from Installing Over a Newer Version


Note Windows Installer uses only the first three fields of the product version. See ProductVersion Property for descriptions of these fields. If you include a fourth field in your product version, the installer ignores the fourth field.


The recommended method of applying a major upgrade by installing the full package for the updated product. For information about how to apply a major upgrade by installing the product, see Applying Major Upgrades by Installing the Product.

A major upgrade applied as a Patch Package for the product cannot be sequenced with other updates and is not an uninstallable patch. For information about how to apply a major upgrade patch package to a Windows Installer package see Applying Major Upgrades by Patching the Local Installation of the Product. The application of a major upgrade using a patch package is not recommended, instead apply major upgrades by installing the full product.


Note If an application is installed in the per-user installation context, any major upgrade to the application must also be performed using the per-user context. If an application is installed in the per-machine installation context, any major upgrade to the application must also be performed using the per-machine context. The Windows Installer will not install major upgrades across installation context.




You can condition custom actions that are sequenced after InstallValidate to handle major upgrades by using the UPGRADINGPRODUCTCODE property:


If you want a custom action to run during an uninstallation of the product, but not during the removal of the product by a major upgrade, use this condition.
REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE

If you want a custom action to run only during a major upgrade, use this condition.
UPGRADINGPRODUCTCODE




Send comments about this topic to Microsoft

Build date: 8/13/2009

© 2009 Microsoft Corporation. All rights reserved.