About surya4u

surya4u · ‎Sep 18, 2012

There are two things you can verify in the project. What is the Schema version are you using. You can find that in General Information -> Summary Information Scheme --> Schema. If it is 405 means the client machine should have windows installer 4.5. If you dont want 4.5 as a minimum requirement you can change that to 301. Regarding the Dot net. Goto tools-->options-->.Net Default scan at build component setting to None. if you not have any dot net modules. may this might help you. Regards, Praveen.

surya4u · ‎Sep 18, 2012

Project Type: Basic MSI Due to some emergency fix in one of the version we have created two dlls with the version 65535.1.0.0 and created the installer. Now those two dlls are having our current version which is 6.1.XXX.XXX. As the installed dlls version is greater than the current version the files are not getting replaced even though I am specifying the Always Overwrite. I have even tried with Override system version but both are not working. Could any one please suggest any other way of overwriting those files due to this we are not able support the upgrade from that version? Regards, Praveen.

surya4u · ‎May 28, 2012

How do you check whether the Patch/HotFix is installed already? 1. Add a VBScript Custom Action (stored in binary table)– CheckIfPatchInstalled ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ''' Function: CheckIfPatchInstalled ''' Purpose: Checks to see if a patch is installed and sets the value of the property ''' 'PATCHINSTALLED' to "true". This property value is used by the Custom action ''' 'CheckIfPatchInstalledError' to display an error. '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Function IsPatchInstalled() Dim sProductCode, sProductVersionHF, sProductVersionCurrent On Error Resume Next sProductCode = Session.Property("ProductCode") sProductVersionCurrent = Session.Installer.ProductInfo(sProductCode, "VersionString") sProductVersionBase = Session.Property("ProductVersion") If (sProductVersionCurrent = sProductVersionBase) Then Session.Property("PATCHINSTALLED") = "true" End If End Function 2. Schedule the CheckIfPatchInstalled as Immediate CA after ISSetupFilesExtract in both Install UI Sequence and Install Exec Sequence with the condition PATCH. 3. Add an Error Custom Action as Immediate CA after CheckIfPatchInstalled in both Install UI Sequence and Install Exec Sequence with the condition PATCH AND PATCHINSTALLED. 4. Add a property PATCHINSTALLED in property manager and leave it empty. 5. Add an Error Custom Action (CheckIfPatchInstalledError) as Immediate CA after CheckIfPatchInstalled in both Install UI Sequence and Install Exec Sequence with the condition PATCH AND PATCHINSTALLED. 6. Add a new Custom Action - CheckIfPatchInstalledError 7. Add the appropriate error message say “25000 - An existing upgrade is already installed. Please remove it before installing this upgrade” to the Error Table in the direct editor and use the Error Number in the CA 8. Create the Patch and apply the patch where the main installer is installed. Running the patch again on the same machine should display the message "An existing upgrade is already installed. Please remove it before installing this upgrade." abort the installation. I hope this will help you.

surya4u · ‎May 24, 2012

I recently joined in this company so I am trying to implement some best practices. As part of that my first step I am trying for Component best practices implementation. Thank you for suggesting me for making it as permanent so here I would like to know some details like If I make it as permanent whether it will be replaced if we want update with Patch/Major release?

surya4u · ‎May 23, 2012

BOD stands for Blue Screen Of Death or Blue Screen Error.

surya4u · ‎May 23, 2012

I have tired the moving the RemoveExistingProducts to CostInitialize. For our product this is not working it is leading to BOD because we are handling the drivers installations. So i dont wan to remove the product before installing the upgrade. Please let me know if there is any other way to handle this.

surya4u · ‎May 22, 2012

Project Type: Basic MSI Brief description: We are planning to support the Patches for our installers. So I have started modifying the project to support the patches. Now in the upgrade scenario it is removing some of our files. Upgrade type: Install setup then remove unneeded files The modifications done for our project are as below. • Applied components best practices. • Previously some components are having dynamic linking so removed them and made them static linking. Some components are with static linking but not having the key files so added key files for those components. • I have not deleted any of the components so the components GUID’s are not changed. From the Log what I found is initially it is installing the files and in the removal of older installation it is removing the files. As previously every component is not having a key file and now I made key file for every component I think it is removing the files. Could any one please suggest how to overcome this problem and we don’t want to change our upgrade type.

surya4u · ‎Aug 16, 2010

Recently we upgrade our installscript MSI project form InstallShield12.0 to Installshield 2010. After upgrading the un-intallation is not working properly. The Problem what we are facing are as follows. 1. Un-installation is only removing the entry form ARP panel. 2. It is leaving all the files in the INSTALLDIR folder. 3. It is leaving the shortcut entries. 4. Leaving all the entries in the registry 5. After un-installations if we are trying to install again it will go to upgrade instead it should start as a fresh installation. 6. While trying to debug it not even entering into script while un-installation. 7. After the installation done if we run the installer again it is going to upgrade mode instead of going to maintenance mode. Note: This project is designed in InstallShield 11.5 then converted to 12.0 It looks like some where the sequence is going wrong. Please help me in the solving this problem

surya4u · ‎Nov 08, 2009

We have an InstallScript Multiple Instance Installer (created with IS2010 Premier Edition) and we are already supporting English, Spanish, Swedish, French, German and Portuguese Languages and the dialog text style & string translation is working fine Now we have a requirement to support East Asian Languages like Chinese & Japanese for our installer. We are facing the following problems 1. Only few strings are converted to Japanese and the rest are in English (which is the default Language in the installer and on the development environment). 2. The dialogues text style is also varying, some dialogues are using MSSansSerif8 & some are MSUIGothic9. Then we tried changing the entire dialogues font to MSSansSerif8 but I am not able to convert “Preparing setup dialog”. So “Preparing setup dialog” looks different when compared to other dialogues. Is there a way where can we set the text style globally & to convert the strings automatically. We are facing this issue only with East Asian Languages. For the remaining Languages it is working fine. Could you please help us with this issue?

surya4u · ‎Sep 23, 2009

If it is basic msi project you can get feature state by MsiGetFeatureState and you can set the feature state by MsiSetFeatureState.

surya4u · ‎Oct 10, 2008

Hi, I am developing one BasicMSI Project. In that i had written the code for browsing a file(here browsing a file is working fine). I want to show that path to the user in the dialog. I am assigning that path to a variable in the script, can we use that variable in the dialog. If yes please let me know how to use it. Thanks & Regards Surya

surya4u · ‎Aug 20, 2008

I am new to BASIC MSI. We are migrating our install script project to Basic MSI project. In our project we have third party installations, how to install third party installer from the basic MSI project. I am looking something similar to the LaunchAppAndWait (used in install script project). I have tried the NESTED installation but it not solving our problem. The third party installer are not MSI setups. Thanks in advance

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Re: Error while adding prerequisite

Unable to replace two files while upgrade.

How do you check whether the Patch/HotFix is installed already?

Re: Upgrade removing the files.

Re: Upgrade removing the files.

Not helping

Upgrade removing the files.

After upgrading the InstallScriptMSI project from InstallShield 12.0 to InstallShie

Localization Issue for East Asian Languages - Dialogues text style & Strings are not

Re: mutilple installation - Basic MSI

Can we call script variables in BASIC MSI Dialogs

How to call third party installation in BASIC MSI

Re: Error while adding prerequisite

Unable to replace two files while upgrade.

How do you check whether the Patch/HotFix is installed already?

Re: Upgrade removing the files.

Re: Upgrade removing the files.

Not helping

Upgrade removing the files.

After upgrading the InstallScriptMSI project from InstallShield 12.0 to InstallShie

Localization Issue for East Asian Languages - Dialogues text style & Strings are not

Re: mutilple installation - Basic MSI