View Full Version : Change log for Beta 2?

04-14-2006, 04:01 PM
Can you please post the bug fixes/changes in Beta 2 for our private viewing?

04-17-2006, 07:41 AM
I'm still putting together a list of all of the resolved issues for InstallShield 12. Here's what I have so far.

Using the C# .NET Wizard to create a new InstallShield project now adds the InstallShield project to the specified Visual Studio 20005 solution.

The IFX_INSTALLED_VERSION variable is now set correctly in InstallScript MSI installations. Previously, the value of this variable was set to 0.00.000 for InstallScript MSI installations.

Clearing the Override System Version check box for a file in a transform project no longer crashes InstallShield.

InstallShield no longer occurs when permissions on some keys in the Registry view are being set.

IOC-000046705 (InstallScript)
InstallShield no longer crashes if you add an executable file (.exe) to a script-defined folder in the Files and Folders view.

IOC-000046696 (Basic MSI, InstallScript, InstallScript MSI)
You can now enter a property as the value for the TCP Port setting on the Web Site tab of a Web site in the Internet Information Services view. Previously, only numbers could be entered for this setting.

The icon specified through the Icon Index setting for an advertised shortcut is now correctly installed.

The Product Version settings are now preserved on the Common tab of a major upgrade item in the Upgrades view. Previously, when you specified a version range with the Version Range Inclusive check box selected, the settings were not saved.

Build error -7115 no longer occurs with the Japanese version of InstallShield when an InstallShield project that contains a DIM is built.

You can now use the Shortcuts view to delete the company name folder and the product name folder that are added to the Program Menu folder when you create a shortcut through the Project Assistant. Previously, if you added a shortcut through the Project Assistant, the only way to delete the resulting company name folder and product name folder for that shortcut was to use the Directory table in the Director Editor.

Visual Studio 2005 no longer hangs when the Custom Action Wizard in InstallShield is run from within Visual Studio.

IOC-000045785, IOC-000045786 (Basic MSI, InstallScript MSI)
The Custom Actions view and the InstallShield Help Library now mention that nested installations is a deprecated feature of the Windows Installer. Microsoft Corporation recommends that you avoid using nested installations and nested-installation custom actions to install products that are intended to be released to the public.

IOC-000045751 (Standalone Build)
When you install the Standalone Build, the installation now creates empty object and merge module folders in the Standalone Build Program Files folder. If your InstallShield projects require any merge modules or objects, you can copy them from the machine that has InstallShield to these new folders on the build machine. Previously, these folders needed to be created manually when the Standalone Build was installed and merge modules and objects had to be added to the build machine.

IOC-000045700 (Standalone Build)
The -o command-line parameter for the Standalone Build (IsSaBld.exe) now works properly: you can use this parameter to specify one or more comma-delimited folders that contain the merge module files (.msm) that are referenced by your project. Previously under some circumstances, using this parameter generated build error -7017, which incorrectly stated that the merge module was not installed on the system.

Components that are associated with a feature through the automation interface are now immediately available through the automation interface. Previously, it was necessary to save, close, and then reopen the project before the component was available through the automation interface.

Migrating an InstallShield Professional 5.5 project to InstallShield 12 under certain conditions will no longer generate error 424, "Object required : IsIsmMigrate.CIsProMigrate.MigrateComponents."

IOC-000045607 (Standalone Build)
The .NET Framework 2.0 redistributables are now installed to the correct Program Files folder for the Standalone Build. Previously, they were installed to the 0409 Program Files folder of the Standalone Build, and this caused a -6247 build error for projects that include the .NET Framework 2.0.

The dynamic InstallScript engine option is no longer supported. As of this release, the installation always uses the engine with which it was built, even if a more-recent version is installed on the target system by a different installation.

IOC-000045420 (InstallScript, InstallScript MSI)
The order in which the setup types are listed in the Setup Types view is the order that is used in the run-time dialog. Previously, changes to the order in the Setup Types view were not reflected at run time.

If a property is contained within an IIS value, but the property has no value, the final installed value will not contain the property. For example, if the name of a virtual directory is Before[MYPROPERTY]After, and MYPROPERTY has no value, a virtual directory will be installed with the value BeforeAfter. Previously, if MYPROPERTY did not exist or had a null value, the installation failed.

The list of servers in the SQLLogin dialog is now case-insensitive. Previously, the list was case-sensitive; therefore, server names were sometimes listed more than once, each instance with different capitalization.

Windows Installer 3.1 v1 is no longer installed on target systems that require v2. For details on platform variants and on acquiring the redistributables, see Microsoft Knowledge Base article 898715.

The caCreateVRoots and caRemoveVRoots custom actions for IIS are now configured with the appropriate conditions: caCreateVRoots has a REMOVE<>"ALL" condition, and caRemoveVRoots has an Installed condition. Both actions need to run during maintenance in case feature selections are changed. Previously, these conditions were not configured for the custom actions; therefore, the progress bar showed these custom actions.

MsiFileHash table entries are no longer incorrectly generated for dynamic file linking.

Specifying a custom icon for an advertised shortcut now works correctly: Build warning 7105 no longer occurs, and ICE03 and ICE50 errors are not generated during validation. Also, the desired custom icon is displayed with the shortcut when it is installed on a target machine. Previously, the Windows icon was sometimes used instead of the custom icon. Additionally, with some earlier versions of InstallShield, users received a 7105 warning at build time and ICE03 and/or ICE50 errors while validating.

IOC-000045233 (InstallScript)
ISProBE.tlb is no longer installed with InstallScript installations; because of the rearchitecture changes, this file is no longer needed. Previously, this file could become corrupted if end users cancel maintenance mode.

IOC-000045147 (Standalone Build)
The XMLRT.dll file is now installed with the Standalone Build. The Standalone Build needs this file to build installations that include XML file changes. Previously, it was necessary to manually copy this file from a machine that had InstallShield to the build machine that had the Standalone Build; otherwise, using the Standalone Build to build installations that included XML file changes caused build warning -5000.

The installation has been updated to include MSXML 3.0 SP5, which is a more recent version of MSXML 3.0 that does not require any dependant merge modules. Previously, an outdated version of MSXML 3.0 that required other merge modules was being distributed.

When the .NET Precompile setting for a component is set to Yes and one of the associated system searches is deleted from the project, an error message is no longer displayed if the .NET Scan at Build setting for that component is changed.

IOC-000043870, IOC-000045034 (Standalone Build)
The instructions for installing the Standalone Build have been updated in the InstallShield Help Library. The instructions now include details about multilanguage and redistributable support.

Setting a predefined folder to a component's destination through the automation interface now results in the correct destination for the predefined folder. Previously, TARGETDIR was always the destination, regardless of the component's destination. Note that the ISWiComponent.SourceLocation property is reset when the ISWiComponent.Destination property is set through the automation interface.

A SQL script that has a multiline string value no longer causes a SQL scripting error on Oracle when it is run from an installation.

InstallShield now properly references results from previous system searches in a Merge Module project by appending the merge module's GUID.

IOC-000044079 (Basic MSI, InstallScript MSI)
If you select the "Requires Windows Installer engine and/or .NET Framework to be installed first" check box for a prerequisite in the Setup Prerequisite Editor, the Windows Installer engine and the .NET Framework are now installed before the setup prerequisite is installed. Previously, the prerequisite was installed before the engine or the framework.

IOC-000043936 (Basic MSI)
Build error -9029 no longer occurs when you build a project referencing a DIM that contains IIS configurations.

IOC-000043797 (Basic MSI)
The Text and Text Style settings for a radio button control can now be modified through the Dialog Editor. Previously, these settings could not be changed.

IOC-000043278 (Basic MSI, InstallScript, InstallScript MSI)
The SQLBrowse dialog no longer crashes or causes an error message when an installation that includes Oracle support runs on a machine that does not have the Oracle client software.

IOC-000043151 (InstallScript)
Dialog skin selection is now remembered properly across invocations of the Release Wizard, no longer resulting in build error 136.

IOC-000043066 (InstallScript, InstallScript MSI
The SQL connection properties are now exported when an InstallScript MSI project is converted to the InstallScript project type.

IOC-000042685 (Basic MSI)
The Login User Information browse dialog now lists only the users available on the selected machine instead of all the users available on all previously browsed machines.

GetDiskInfo now returns >= ISERR_SUCCESS when only DISK_INFO_QUERY_DRIVE_TYPE is specified for nInfoToQuery. Previously, ISERR_GEN_FAILURE (-1) was returned. Also, the function now returns < ISERR_SUCCESS when a null pointer is specified for pdi. Previously, the function could cause the installation to crash when the function was called with a null pointer. Also, a new structure member called nResultDiskSpace is available to obtain the result of attempting to query other information. For more information, see the InstallShield Help Library.

If the Path member of the ISWiSetupFile object in the automation interface contains a path variable, the path variable is now resolved to the actual path. Previously, path variables were not resolved.

COM+ passwords are no longer visible in verbose Windows Installer log files; asterisks are used to obfuscate the passwords.

IOB-000003487 (Basic MSI and InstallScript MSI)
Log files and reports are now displayed in the Releases view, regardless of how the Shallow folder structure setting is configured. Previously, if Yes was selected for the Shallow folder structure setting, log files and reports were not displayed in the Releases view.

Changing the settings for one previous setup in the Patch Design view no longer simultaneously changes the settings for other previous setups that are part of the same patch configuration.

IOC-000042302 (Basic MSI, InstallScript MSI)
When you clear the check box for a COM+ application in the Component Services view, the COM+ application—including its components and any corresponding information in the ISCom* tables—is now completely removed from the project.

IOC-000040940, IOC-000047820
The In-Script Execution setting in the Custom Actions view and in the Respond Options panel of the Custom Action Wizard now includes the following three options: Rollback Execution in System Context, Commit Execution in System Context, and Deferred Execution (Terminal Server Aware).

IOC-000040915 (Basic MSI, InstallScript, InstallScript MSI)
The Internet Information Services view now supports the creation of a child virtual directory within a parent virtual directory. Previously, this was only possibly by adding a backslash to the display name of the directory.

IOC-000040570 (Basic MSI)
Two settings have been added to the List View control in the Dialog Editor: Icon Size and Stretch to Fit. Also, editing the List View controls that have icon images no longer creates unused entries in the Binary table.

The typographical errors in the example code provided on the REGDB_OPTIONS help page in the InstallShield Help Library have been corrected. The correct spelling is REGDB_OPTIONS. Previously, the examples omitted the underscore.

IOA-000008306 (Basic MSI, InstallScript MSI)
The MSI 3.1 Engine URL setting in the Releases view now contains a default value for projects that are upgraded from DevStudio 9. Previously, this setting was blank for upgraded projects.

Dialogs that have radio button controls are now imported correctly from resource DLLs. Previously, some of the dialog controls were missing after import if the radio button text had more than 64 characters.

IOC-000034768 (Basic MSI, InstallScript MSI)
Some significant performance improvements have been made to the Component Services view. It now takes approximately 15 minutes to import a particular large-scale COM+ application into a project; previously, it took more than 18 hours to import this same COM+ application.

1-XCEFH (InstallScript)
The ellipsis button (...) has been removed from the Display Icon setting for Add or Remove Programs in the General Information view. Also, the Display Icon Index setting has been added so that you can specify the icon if more than one icon resource is included in the file.

The help pane for the Company Logo setting in the Update Service view now lists the correct dimensions for a custom graphic in the Update Service wizard. Previously, the width and the height dimensions were mixed up.

If you create a new project by opening an existing project and saving it with a different file name, the new InstallShield project file (.ism) and all of the associated project files—including Setup.rul script files—are writeable. Previously, some of the files were writeable, but some were read-only.

1-ID3OX (InstallScript, InstallScript MSI)
The Dialog Editor now has a Resource Identifier setting for dialogs.

1-EJLM5 (InstallScript)
The VS .NET Project Output setting in the Shortcuts view has been disabled for Internet shortcuts because it does not apply to this type of shortcut.

The Comments property has been added to the ISWiShortcut object in the automation interface.

The InstallShield Help Library now includes detailed information on how to upload and release a COM object that has been loaded by the script. To learn more, see the following help topics: "Extending Your Installation with COM Objects," "CoCreateObject," "CoCreateObjectDotNet," and "CoGetObject."

When predefined InstallScript dialogs are edited, InstallShield no longer creates icon files if they already exist.

The build engine can now handle a directory path that contains a semicolon. Previously, if an InstallScript project included a dynamic or static link to files in a folder that has a semicolon in its name, build warning 5000 occurred, and no files from that folder were included in the built release.

1-1B3BSJ (InstallScript, InstallScript MSI)
Cloning a dialog in InstallScript and InstallScript MSI projects no longer creates a Behavior subnode for the newly cloned dialog. Previously, the Behavior subnode was added for a dialog during cloning, and clicking the Behavior subnode caused InstallShield to crash. Basic MSI projects support the Behavior subnode, but InstallScript and InstallScript MSI projects do not.

1-1AEAK3 (InstallScript, InstallScript MSI)
If you modify the ScrollableText control on the SdLicense2RTF dialog, the RTF file is now displayed at run time. Previously, the RTF file was not displayed at run time if this control had been modified.

1-19QYUJ (InstallScript)
The After Move Data event category is now displayed under the Move Data event category in the InstallScript view to reflect the chronological order of these events. Previously, the After Move Data event category was listed above the Move Data event category.

1-19JANT (Basic MSI)
You can no longer change the name of one dialog control to match the name of another control on the same dialog; if you try to do this, InstallShield displays a warning because the name duplication could cause a circular reference in the Control table. Previously, InstallShield allowed you to replace the name of one dialog control with the name of a dialog control that already exists on the same dialog. This sometimes led to unexpected results: InstallShield locked up or one of the controls disappeared from the dialog.

1-14NI9O (Basic MSI)
If you use the Direct Editor to modify the Text column of the Control table—or any columns of the RadioButton, CheckBox, ComboBox, or ListBox tables—the Dialogs view is now refreshed accordingly. Previously, the only way to see those types of changes reflected in the Dialogs view was to save, close, and then reopen the project.

The list of recently opened projects on the Start Page is now updated as soon as you open or create a project. Previously, it was necessary to close and then reopen InstallShield in order to see an updated list of recently opened projects.

If you launch the Component Wizard from a specific destination folder in the Files and Folders view, the destination that is selected by default in the Component Wizard is the same one from which you launched the wizard. Previously, the destination location that was selected by default was always [INSTALLDIR].

When a component is exported to a merge module project, the value of the ProgId_Default column of the Class table is no longer populated with the merge module GUID.

GetDiskInfo with the DISK_INFO_QUERY_DRIVE_TYPE parameter now returns correct information on Windows 9.x platforms. Previously in some cases, the function would set di.nDriveType to DRIVE_NO_ROOT_DIR instead of getting the actual drive type.

InstallScript API WriteProfString now flushes the .ini file buffer for the specified .ini file on Windows 9.x when "" is specified for all the parameters except the .ini file name.

Note: The following existing Windows API prototypes in WinAPI.h have changed:

prototype KERNEL32.WriteProfileStringA(BYVAL STRING, POINTER, POINTER);

are now:

prototype KERNEL32.WritePrivateProfileStringA(POINTER, POINTER, POINTER, BYVAL STRING);
prototype KERNEL32.WriteProfileStringA(POINTER, POINTER, POINTER);

An implication of this change is that if you are calling WritePrivateProfileStringA or WriteProfileStringA in your script, your script code will not compile because the first parameter must not be specified as a POINTER. That is, you may get a message similiar to:

C:\My InstallShield 12 Projects\My Project Name\Script Files\Setup.Rul(20) : error C8038: 'szAppName' : numeric value required

In order to resolve this problem, instead of passing the variable, pass a pointer to the variable. Use this:

WritePrivateProfileStringA( &szAppName, &szKey, &szValue, szFileName );

Do not use this:

WritePrivateProfileStringA( szAppName, &szKey, &szValue, szFileName );

InstallScript MSI patches that are built under certain specific conditions no longer generate a run-time error that indicates that the setup must be launched from Setup.exe.

Installing the .NET Framework 1.0 onto Windows XP Tablet PC Edition will no longer attempt to apply SP3 (which failed because it is a system component and must be applied as part of Windows XP Tablet PC Edition SP2).

Passing eptProObj to the ISWiProject.CreateProject method of the automation interface no longer causes an exception error.

IOC-000045787 (Basic MSI, InstallScript MSI)
The Device Files panel of the Windows Mobile Wizard has a new check box setting that you can configure to suppress the warning "The program you have installed may not display correctly because it was designed for a previous version of Windows Mobile software." Previously, if a .cab file appeared to target only newer platforms, BuildMax=0xE0000000 was added to the [CEDevice] section of .inf file, suppressing the warning. However, there may be cases where the setup author always wants to suppress the warning, so selecting this new check box will always add BuildMax=0xE0000000 in the .inf file.

When you choose the Existing Mobile Device Cabinets option in the Windows Mobile Wizard, all .cab files that are added through the wizard are automatically installed on the target machine. Previously, only one of the .cab files was automatically installed.

Windows Mobile installations will now automatically launch the latest mobile installation during the repair and upgrade scenarios. Previously, the ActiveSync Add or Remove Programs applet was launched, but the latest installation was not automatically launched. Now, users will automatically get the option to repair/upgrade their mobile application.

IIS 6 support now allows for overwriting existing Web service extensions. To enable this, select the new check box on the Web Service Extension tab in the Internet Information Services view. Previously, installations could only create new Web Service Extensions. This feature will allow setup authors to allow or prohibit extensions that already exist on the target machine.

Debbie Landers
Macrovision Corporation