Having to include SQL scripts in our installation soon, I am investigating the SQL Scripts functionality. Running the scripts in a test install worked fine, until I added a Schema Version using the format as shown in the label on top of the textbox: Schema Version (xxxxx.xxxxx.xxxxx.xxxxx): So nicely entering 00000.00000.00000.00001 as the Schema Version caused the error (as described by fmshafiq) to appear. This thread helped while after changing the Schema Version to 0.0.0.1, everything works as expected. However, originally I entered a value in the expected format xxxxx.xxxxx.xxxxx.xxxxx (obviously string length 24) that apparently is longer than the expected string length for the column that is supposed to contain it. hidenori wrote: The data type of the column that stores schema versions is defined as char (15). The string length of your schema version is longer than expected. To get it workaround, you need to change the data size of the ISSchema column of the InstallShield table ... It would be nice if the data type of the column and the Schema Version format are in sync, e.g. a format of xxx.xxx.xxx.xxx (string length 15) is suggested on top of the Schema Version textbox. ... View more

Yes, I am facing the same problem. Also in the context menu of Start Menu programs both Pin to Taskbar and Pin to Start Menu are missing. ... View more

If you are working with a Basic MSI Project, you may want to define your own theme and use that to change the looks of all dialogs. ... View more

Typically you can use whatever Path Variable in the Defined Value of some other Path Variable. E.g. Name Defined Value MyProjectRoot C:\Test\MyProjects MyProjectFiles \MyFiles As you can also create an Environment Path Variable here by clicking on the down arrow next to New, I suspect the value of the corresponding Environment Variable will be used. So I would try to define MyProjectRoot as an Environment Path Variable and use the MyProjectFiles Path Variable in the Link To. The names used here are just for the sample. Obviously you can use other names. Personally I am using ISProjectFolder in my Path Variables as the release builds are done on another machine using ISCmdBld.exe. ... View more

Looking at the command line "C:\Program Files\7zip\7za.exe" e "C:\Program Files\OC4J\oc4j.zip" "-oC:\Program Files\OC4J" I notice that the -o is also inside the quotes. Shouldn't you have to specify the following: "C:\Program Files\7zip\7za.exe" e "C:\Program Files\OC4J\oc4j.zip" -o"C:\Program Files\OC4J" That is, -o"C:... instead of "-oC:... ? ... View more

Just to be sure: did you really use %ProgamFiles% (instead of %ProgramFiles%) or is this a typo in you message? ... View more

As far as I know you should use Disable(BILLBOARD), not Disable(BACKGROUND). Further, I suspect the condition in the if-statement should be REMOVEONLY instead of !REMOVEONLY, that is if REMOVEONLY is the value to test for in your situation. ... View more

Hello Vijay, you might set some other property in you custom action and use that property in the control's Condition tab. Eric-Paul ... View more

Sure, we added a custom InstallScript action (between AppSearch and LaunchConditions) that checks for the OS and sets the INSTALLDIR property accordingly. This gives us an OS dependent default location for the software. ... View more

What I have done (and what is working) is the following: The radio buttons I use the radio button group with the property _IsSetupTypeMin In this group I have a radio button for each setup type Each radio button has a name that starts with _IsSetupTypeMin and ends with a sequence number , _IsSetupTypeMin1, _IsSetupTypeMin2, ... Each radio button has a value and this value will be assigned to the _IsSetupTypeMin property when checked In my setup I have a type for a complete installation, a custom installation and several types for different configurations. To get something like this working, you need to adjust the behavior of the Next PushButton accordingly. For instance, I have added events | arguments | conditions such as: The behavior [LIST=1] AddLocal | ALL | _IsSetupTypeMin = "Typical" Remove | ALL | _IsSetupTypeMin <> "Custom"AND _IsSetupTypeMin <> "Typical" AddLocal | MyServer | _IsSetupTypeMin = "Server" AddLocal | ManagementTool_1 | _IsSetupTypeMin = "Management" AddLocal | ManagementTool_2 | _IsSetupTypeMin = "Management" and so on ... This controls the features that will be installed based on the setup type you select. I hope this helps you. ... View more

Hello Ron, you're quite right, be carefull. The OS that I based my findings on is Windows 7 (64-bit). I have then first installed Visual Studio 2008 which in turn caused SQL Server 2005 Express to be on my machine. I had to uninstall that to get the proper stuff installed for SQL Server 2005. Consecutively, I installed SQL Server 2008. ... View more

Hello Shaun, you can set up an InstallScript Custom Action and implement the search yourself in the corresponding InstallScript function using RegDBxxx functions such as RegDBSetDefaultRoot, RegDBKeyExist and so on. Having found the correct path, you can then set INSTALLDIR accordingly. Eric-Paul ... View more

Hello Ron, If 'Microsoft SQL Server 2005 Backward Compatibility' is installed, the following key should be present in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\328F2D26AAE0D6940B9F8A96FB5C5105 You might setup a system search for this registry entry and set some property you might use during setup. Eric-Paul ... View more

Facing the same challenge, we have created a DLL (C++) for checking the serial number we call it in an InstallScript function and feed the value of the ISX_SERIALNUM property to it. based on the result (0 or 1, just like your DLL) we set a custom property LICENSE_OK we created a custom action CheckLicense for this function in the Customer Information dialog's Next pushbutton behavior we have added several events [LIST=1] event: DoAction | argument: CheckLicense | condition: 1 event: EndDialog | argument: Exit | condition: not LICENSE_OK AND check for number of failures to enter a correct license code event: NewDialog | argument: SetupType | condition: LICENSE_OK event: SpawnDialog | argument: SomeDialog (indicating wrong license code) | condition: not LICENSE_OK I hope this will also work for you. ... View more

If you follow Josh's suggestion, you might check yourself whether the IIS 6 metabase compatibility has been installed. Once you know this for the appropriate platforms, you might use the mentioned property or not or do something else. For detecting whether the IIS Metabase and IIS 6 Configuration Compatibility feature is set, there is a sample DLL with source code available in the following folder: C:\Program Files\InstallShield\2010\Samples\WindowsInstaller\Detect IIS6 Compatibility ... View more