You can create separate components for 32 and 64 bit in area of Website and application pool. And then put condition on their components. SO in the end you will be getting 4 components 2 for web site and 2 for app pool. Other ways you can publish separate installers for 32 and 64 bit OS. ... View more

Try the following Take a copy of Installshield project source files that you used in last major release. Now paste all the changed files for minor upgrade on the location above. And use these files to create a minor upgrade. ... View more

Go to Patch design --> Select patch configuration --> Expand the previous setups --> Click previous setup Click on Advanced tab Under the transform filter settings set Version Relationship => Previous setup version = latest setup version Version to check => Check Major and Minor version ... View more

If there is no command line switch required to run your executable then keep the command line field empty from your custom action. ... View more

You can create your own prq by navigating Tools--> Pre req. editor ... View more

The best way to do this is use the same upgrade code in the installshield project as used by the other tools. In case you have multiple upgrade keys then this method won't work. So first you need to make sure that the upgrade code of all your older installers is same. ... View more

In installshield project you can include your sql scripts in the SQL section of the project and you can also use the default sql dialog available in the project to get the input from the user during the runtime of the installer. ... View more

If you are installing the patch like Initial + Jan fix + Feb fix it will work absolutely fine. On other case where you are supplying Initial+Janfix as a major release, in that case the Feb fix you supplied above will not work for this new release. for this you need to create another patch release. ... View more

Try the condition (&FeatureName=3). By this condition your custom action will run only when the Feature is selected to install. ... View more

Try this http://www.microsoft.com/en-in/download/details.aspx?id=5793 ... View more

srout2000 wrote: I have a custom action in an Installshield Basic MSI project to find out the version of SQL Server from registry. RegKey2012 = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\" & _ "Microsoft SQL Server\MSSQL11.MSSQLSERVER\" If RegKeyExists(RegKey2012) Then WScript.StdOut.Write("2012") Else WScript.StdOut.Write("2008R2") End If Function RegKeyExists(Key) Dim oShell, entry On Error Resume Next Set oShell = CreateObject("WScript.Shell") entry = oShell.RegRead(Key) If Err.Number <> 0 Then Err.Clear RegKeyExists = False Else Err.Clear RegKeyExists = True End If End Function The installer works fine on a Windows 7 machine. The above script works fine in isolation on a Windows Server 2012 machine. However when I run the installer (as ADMIN) on windows server 2012, it does not work as expected and the error description is - It cannot find the registry key. Any ideas. Why don't you try System Search option to detect the registry entry? ... View more

Did you mean that you have an installation dialog with a check box control on it, and you want to change the behavior of the Next button on the dialog based on the user selection or unselection of check box control? ... View more

Found the solution. Unselected the dll as key file from the component. ... View more