This product offers you two choices for authoring installations: Wise Installation Studio or Wise Installation Express. Both products build on established Wise technologies.
Wise Installation Studio is an advanced installation authoring tool that supports both Windows Installer (.MSI) and WiseScript installations. Wise Installation Studio is a comprehensive collection of tools and technologies for creating software installations for Windows devices:
Wise Installation Express is a basic installation authoring tool that supports Windows Installer installations. Wise Installation Express consists of the following tools:
In effort to simplify our product lines, we have discontinued the Wise for Windows Installer and Wise Installation System product lines. The technologies that were in those products are now included in Wise Installation Studio and Wise Installation Express.
Please read the following information carefully before using this software. It contains details on new features, enhancements, and other changes to the product.
You Have the Correct Upgrade?
Known Issues in 7.0
Windows Vista Support in 7.0
Installation Notes for 7.0
Upgrading to 7.0 from an Earlier Version of Wise Products
Enhancements in 7.0
Other Changes in 7.0
Enhancements in Windows Installer Editor 7.0
Other Changes in Windows Installer Editor 7.0
Enhancements in WiseScript Package Editor and WiseScript Editor 7.0
Other Changes in WiseScript Package Editor and WiseScript Editor 7.0
If you are upgrading from a previous Wise installation product, verify that you have received the correct upgrade.
|If you were using:||then upgrade to:|
|Wise for Windows Installer—Standard Edition||Wise Installation Express|
|Wise for Windows Installer—Professional or Enterprise Edition||Wise Installation Studio|
|Wise Installation System—any edition||Wise Installation Studio|
Back to Contents
Can't compile a clean build. (44351) In Windows Installer Editor, on the Clean Build page, when you selected the option to store the clean build in source control, the Wisebuild.exe file was not added to source control. Therefore, you could not build the installation when you checked out the source files to a clean machine. This has been fixed. However, double-clicking Wisebuild.exe to compile the build does not work. To work around this problem, double-click wfwi.exe instead, which will perform the compile. For updated information, see Knowledgebase article 29210.
Re-installing. (50226) If you uninstall Wise Installation Studio and re-install it, the Altiris Software Virtualization Agent (SVS Agent) does not get reinstalled. For updated information, see Knowledgebase article 29212.
Recompile does not include added prerequisites. (54612) In Windows Installer Editor, when you add a prerequisite or runtime on the Prerequisites page and compile, the prerequisite or runtime is added to the WiseScript (.wse) that creates the installation .exe, and resulting .exe contains the prerequisite or runtime file. However, if you add an additional prerequisite or runtime and then recompile, the .wse is not regenerated and the .EXE does not contain the additions. To work around this issue, delete the .wse that resulted from the initial compile and then recompile. The .wse will be regenerated and the .exe will contain any additional prerequisites or runtimes. For updated information, see Knowledgebase article 29379.
Back to Contents
Wise Installation Studio and Wise Installation Express have been tested on build 5600 of Windows Vista*, which corresponds to the RC1 release*. Because a production version of Windows Vista was unavailable at the time of this release, you might encounter unexpected results on other versions of Vista.
This product's Vista support includes the following:
- The ability to run Wise Installation Studio or Wise Installation Express on Windows Vista, with these exceptions:
- The ability to add Vista support to your Windows Installer packages:
* Windows Vista support in this product includes but is not limited to Altiris' product readiness statement for Windows Vista, which is based on a pre-production release (build 5600) and may be considered "forward-looking." Such forward-looking statements are based on current expectations and involve certain risks and uncertainties that could cause actual results to differ from such forward-looking statements. Such risks include potential changes to Windows Installer 4.0 or the core operating system (Microsoft Windows Vista). These risks should be taken into account when purchasing any software. We therefore cannot provide any assurance that such forward-looking statements will materialize according to their current form. However, Altiris is dedicated to supporting Microsoft Windows Vista with Wise Installation Studio and Wise Installation Express.
Back to Contents
Installing this product on Windows Vista. Follow the procedure below to install Wise Installation Studio or Wise Installation Express on Windows Vista. This procedure was tested with build 5600 of Windows Vista (RC1), on SQL Express 2005.
SVS compatibility. Wise Installation Studio 7.0 requires the Altiris Software Virtualization Agent (SVS) 2.0, build 2.0.1393 or later. The latest SVS installation as of this release is included in the Wise Installation Studio installation.
Installation files. This product's installation is run from an .exe that installs Wise Installation Studio or Wise Installation Express and an informational dialog about Nalpeiron PRO-Tector. The Wise Installation Studio installation also installs the Altiris Software Virtualization Agent. During installation, the Wise Installation Studio/Express .msi file is extracted to \Program Files\Altiris\Setup Files\Wise Installation Studio. The Software Virtualization Agent .msi file is extracted to \Program Files\Altiris\Setup Files\Software Virtualization Solution. Do not delete these files because they are needed for future repairs.
Installing this product with other Wise products. Wise Installation Studio and Wise Installation Express cannot be installed on any computer that contains any edition or version of Wise Package Studio, Wise for Windows Installer, or Wise for Visual Studio .NET.
Installation directory. The default installation directory is Program Files\Altiris\Wise Installation Studio or Program Files\Altiris\Wise Installation Express.
Documentation locations. The Release Notes and Getting Started Guide are available from the Windows Start menu, under Start > Programs > Altiris > Wise Installation Studio or Wise Installation Express. Documentation for each tool is available from the tool's Help menu.
Visual Studio integrated editor tutorial. If you install Visual Studio after you install Wise Installation Studio or Wise Installation Express, some of the files you need for the Visual Studio integrated editor tutorial are not installed. To install these files, perform a repair on the Wise Installation Studio or Wise Installation Express installation.
Back to Contents
Uninstalling a previous version. Before you run the Wise Installation Studio or Wise Installation Express installation program, uninstall any previous version of Wise for Windows Installer or Wise Installation System.
Connecting to a Wise Software Repository. If you are upgrading to Wise Installation Studio from Wise for Windows Installer Enterprise, you can continue to connect to a Wise Software Repository to share installation resources. This release requires that the repository be configured for Wise Package Studio 7.0 SP1 or later. However, the Wise Installation Studio installation does not create or upgrade the repository; all repository operations are handled by the Wise Repository Manager, which is available only with Wise Package Studio.
To connect to an existing Wise for Windows Installer repository:
To connect to an existing Wise Package Studio repository:
Back to Contents
Integration with Altiris Software Virtualization Solution (SVS). (Wise Installation Studio only.) In Windows Installer Editor, you can install an installation into a virtual layer and then delete the layer to restore the computer to its original state.You can use Virtual Package Editor to create and edit virtual software packages and the Altiris SVS applet to manage layers.
Expanded Mobile Device Package Editor. (Wise Installation Studio only.) Previously, the Mobile Device Package Editor provided limited functionality for creating a simple .cab file or editing the resources of an existing .cab file. Now it is a complete mobile device installation development tool. Using an interface that is similar to that in other Wise installation development products, you can easily create a project file in .inf format and compile it to one or more .cab files that install a mobile device application. For advanced customization, you can edit the .inf directly within the Mobile Device Package Editor.
Product Home pages. The following tools have a Home page: Windows Installer Editor, WiseScript Package Editor, Mobile Device Package Editor, and Virtual Package Editor. The product Home page provides quick access to areas of the current project and access to Wise resources on the Internet. To go to the Home page, click Home at the lower left of the main window. If you do not have an Internet connection, a static home page, which is installed with the product, is displayed. If you are connected to the Internet when you start the software, a dynamic page is downloaded from the Wise Web site.
Digital signature support. Support for the signtool.exe code signing tool has been added to the Digital Signature page in both Windows Installer Editor and WiseScript Package Editor. The file signing tool that is used to digitally sign the installation depends on the type of your digital certificate:
Back to Contents
Note: The numbers that precede the items below are issue tracking numbers.
Documentation locations. The Release Notes and Getting Started Guide are no longer available from the product's Help menu. They are available from the Windows Start menu, under Start > Programs > Altiris > Wise Installation Studio or Wise Installation Express.
51405: In MSI Script, if you added or moved a custom action over an existing custom action that was in an if condition block, Windows Installer Editor crashed. This has been fixed.
51494: In MSI Script, Windows Installer Editor crashed when you selected the Execute Immediate tab for some .MSI or .WSI files. This has been fixed.
Back to Contents
Windows Installer Editor is comparable to previous versions of Wise for Windows Installer.
Expanded 64-bit support. Windows Installer Editor supports installations that contain only 32-bit components, installations that contain only 64-bit components, and installations that contain both 32-bit and 64-bit components. Windows Installer Editor supports both x64 (for AMD64 and Intel EM64T processors) and 64-bit Itanium platforms.
The target platform is stored in the Template Summary property of the .msi or .msm (merge module). For an installation to run, the platform in the Template Summary property must match the platform of the destination computer. The Template Summary property of the .msi is set during compile based on the releases Target Platform setting. The initial target platform for the Default release is set by the Target Platform option on the New Installation File dialog. You also can set the target platform on the Feature Details dialog and on the Component Details dialog.
You can create a single installation project (.wsi) that can produce 32-bit and 64-bit installation files, or x64 and Itanium installation files. To do so, on the Releases page, create a release for each target platform. Then, on the Release Settings page, include features and components in the appropriate releases.
In a 64-bit installation:
The Target Platform tab has been removed from the Wise Options dialog. Also, the Target Platform option has been removed from the Wise Setup Wizard in the Visual Studio integrated editor.
Support for the Windows Vista Logo Program. Package Validation contains a new validation module, Windows Vista Compatibility Checks (WiseVistaIce.cub), which checks for adherence to the requirements for Microsofts Windows Vista Logo Program certification.
Windows Installer Options page. Use Installation Expert > Windows Installer Options page to enable the following features for installations that will run on Windows Installer 4.0 or later.
Support for Vista standard user installations. (For Windows Installer 4.0 or later.) The User Account Control (UAC) described above provides a temporary privilege-elevation model for running installations that require elevated privileges. However, if an application has been written to be installed and run by standard users without elevation, you can bypass UAC issues. To create a standard user installation, do one of the following:
Support for Nalpeiron copy protection. (Wise Installation Studio only.) When you purchase a Wise Installation Studio license, you can obtain one free license of the Nalpeiron PRO-Tector Trialware solution, Standard version, which lets you create copy-protected trial and demo versions of Windows applications. You can add Nalpeiron copy protection to an installation by:
Add a digital signature to patches. You can use the Specify Digital Signature Settings dialog in the Patch Creation tool to add an Authenticode digital signature to a patch file. Frequently, updating an application requires higher privileges than those of a standard user, and only the administrator has sufficient privileges to run the update. This can result in the application needing to be run with administrator privileges. You can avoid this problem by signing patches that will be run under Windows Vista. When the patch is applied, Windows Vista performs the elevation for the application.
Manage Assembly Exclusions. When you add a .NET assembly to an installation, and you choose not to add one or more of the assembly's dependencies, those dependencies are added to an exclusion list for that installation, which means that the assemblies never appear during a rescan. This is by design. In the past, however, clicking the Cancel button on the Assembly Dependencies dialog added all the dependencies to the exclusion list, whether or not their checkboxes were marked, without any indication to the user. The following changes have been made:
Remove files with missing or invalid source paths. When you compile an installation that contains files with missing or invalid source paths, the compile fails. The Remove Missing Files tool reduces compile errors by searching an installation for such files and letting you remove those files from the installation. It provides an option to compile after you remove files. To access the tool, select the Tools menu > Remove Missing Files.
Mobile Devices page. The Mobile Devices page is no longer used to create mobile device .CAB files. Instead, use the Mobile Device Package Editor, which is now provided as a separate tool in Wise Installation Studio. Use the Mobile Devices page to configure a Windows Installer installation to install files that support a mobile device application. (To see the Mobile Devices page, select one of these views from the Page Views drop-down list in Installation Expert: All, Palm Application, or Windows Mobile Application.) The following platforms are supported:
The mobile device installation files are included in the compiled .MSI or .EXE. If you added Windows Mobile .CAB files, an .INI file that describes the .CABs is created and included in the compiled .MSI or .EXE.
WiseUpdate enhancements. (Wise Installation Studio only.) The following options have been added to the Installation Expert > WiseUpdate page:
Increment the product version automatically. You can increment the product's version number during compile by marking the Increment version number on compile checkbox on the Product Details page. This increments the third segment of the version number. Examples: 3.0.3790 is incremented to 3.0.3791, 2.5 is incremented to 2.5.0001.
Features page. In the drop-down list that appears when you click the icon next to a feature, the Entire feature will be unavailable option has a new icon.
Files page. The default directory that you specify on the Product Details page appears on the Files page followed by [INSTALLDIR]. This makes it easy to identify the installation directory on the Files page. You can deactivate this option from the right-click menu.
Prerequisites page. Additional runtimes have been added to the Runtime Details dialog. To access this dialog from the Prerequisites page, select Add > Runtime.
Multiple file permissions. You can set permissions for multiple files at the same time. You can do this in Installation Expert on the Files page and in Setup Editor on the Features or Components tab.
Registry key permissions. You can now set permissions on registry keys instead of registry key names. You access the Registry Key Permissions dialog on the Registry page by right-clicking the key and selecting Permissions.
System Requirements support for Internet Explorer 7.0. In Installation Expert > System Requirements page, an option to support Internet Explorer 7.0 was added to the Internet Explorer Version requirements.
Windows XP logo verification. A new validation module, Windows XP Application Specification Logo (XPlogo.cub), has been added to Package Validation. It is provided by Microsoft as part of its Windows XP logo verification program. The tests in XPlogo.cub are a subset of the tests in darice.cub.
Display full directory path in Directory and Component tables. In Setup Editor > Tables tab, the Component and Directory tables resolve and display the full path values for the directories listed in the tables. This is especially useful in the Components table, which does not list the parent directories. Example: In the sample QuickFacts installation, the Components table lists the directory for the help file as Help. The resolved value for the Help directory is Program Files\QuickFacts\Help.
Merge module template. The merge module template, which is used when you create a new merge module, has been updated to support Windows Installer 2.0 installations.
Windows Installer SDK help. This product includes the 3.1 version of the Windows Installer SDK help (msi.chm).
.NET Compact Framework 2.0. You can download .NET Compact Framework 2.0 from the Wise Web site when you select Help menu > Download Redistributables.
Command line support in Debugger for Windows Installer. You can set properties and apply transforms to installations that you test by running the debugger (Debugger.exe) from the command prompt and using standard Windows Installer command line options.
Back to Contents
Windows Installer Editor is comparable to previous versions of Wise for Windows Installer.
NOTE: The numbers that precede some items below are issue tracking numbers.
Visual Studio integrated editor performance. Improved the performance of the Visual Studio integrated editor when you add folders containing a large number of files. Also added progress bars where necessary during long dependency scanning and file addition processes.
Preventing dialog control disappearance. When dialog controls are layered on top of a graphic or other control, the tab order determines the layer order. During compile, any item that is not included in the tab order is layered over items that are included in the tab order, causing certain controls to be hidden at run time. This layering can change from compile to compile. This is a Windows Installer limitation.
Previously, in the default templates, the dialog tab order did not include the graphics. It has been updated to include the graphics in the tab order.
To prevent unexpected control layering in existing installations, or when you create or customize a dialog, set the dialogs tab order to include any graphic or control that is overlapped by another control. The higher the item is in the tab order, the closer to the top layer it will be.
Custom templates. Fixed minor issues with custom installation templates:
Disabled the Command Line page in a transform. Because you cannot apply a command line to a transform, the Command Line page is disabled when you are working in a transform.
Save As command. (Visual Studio integrated editor only.) The Save As command is disabled for an installation that is part of a solution, because performing a Save As on such an installation causes problems with the solution.
30780: When .NET .DLLs were added to the Global Assembly Cache, the file was not installed into the Assembly folder. This has been fixed.
32752: Some dialogs use a conditioned Wise Next Dialog event, and a corresponding DoAction > WiseNextDlg action in the ControlEvent table. The conditions for these events/actions were not linked properly. As a result, the DoAction > WiseNextDlg action would execute (and increment the dialog counter), but the Wise Next Dialog event would not execute, resulting in a mismatch that caused Windows Installer 2856 errors. This issue has been fixed to reflect the condition in both the DoAction and NewDialog components of the Wise Next Dialog event. Also, this problem is fixed in existing installations when you open them in Windows Installer Editor.
35159: In an installation with multiple languages, when you updated any control details in the Default language, any translations for that control reverted to English. This has been fixed so that the translated text reverts to English only if you change the control's text in the Default language. If you make any other changes to the control, the translated text is not affected.
35693: Table errors occurred when you compiled an installation that had multiple releases with Web files in one feature. When the Web .MSI was run, its files were installed but its virtual directory was not created. This has been fixed.
37197: Fixed a problem that caused an invalid path when a folder and its contents were added to a virtual directory on the Web Files page.
37295: In a new custom table, the drop-down for foreign-key fields would not appear until after the product was restarted. This has been fixed.
38162: When an installation that contains the SQL Connection dialog was run, and the end user clicked the Browse button at the SQL Server Name field, the Browse dialog was not always populated correctly. This has been fixed.
38165: Fixed a problem that caused Server Application .MSIs to skip the Start Installation dialog.
38236: For Web applications, feature conditions were not applied correctly on IIS dialogs. This has been fixed.
39103: In a 64-bit installation, when you entered a registry search on the System Search page and you marked the option to search the 64-bit portion of the registry, the search settings were cleared when you closed the dialog. This has been fixed.
39400: Fixed problems that caused the Move Components to Merge Module tool to move data incorrectly or not at all.
39847, 39848: When tooltip information was entered for a radio button group, the RadioButton table was not populated correctly. To resolve this issue, the Help tab has been removed from the Properties dialog for radio button controls. To enter tooltip help for a radio button control, click the Items tab on the Properties dialog, click Add or Details to display the Radio Button Details dialog, and enter the tooltip text in the Help Text field.
40252: Fixed a problem that caused Web applications that had multiple virtual directories to convert incorrectly when opened with a later version of this product.
40817: Compiling multiple times after modifying the Release Settings page caused a Windows Installer error 2709 in the resulting .MSI. This has been fixed.
40829: Normally, when you click the Test button, the installation is recompiled if it has changed since the last test. Web Application installations were not recompiled after a Web Site was converted to a Virtual Directory. This has been fixed.
41112: The Move Components to Merge Module tool did not transfer rows from the LockPermissions table to the resulting merge module. This has been fixed.
41348: When using the Move Components to Merge Modules tool, companion file entries were not transferred to the merge module. This has been fixed.
41514: The Web Application template has been updated to include a system requirement check for IIS 4.0 by default.
41608: Prerequisites page: Normally, if you enter a prerequisite file, and the build options for the installation are set to create an .exe that launches an external .msi, then when the installation is compiled, the prerequisite .exe is copied to a subdirectory of the installations project directory, named msiname\FILEPATH1. If the prerequisites script was changed, the prerequisite .exe was not getting copied to the FILEPATH1 directory. This has been fixed.
41610: During compile of an installation that contains a prerequisite file and has build settings that create an .exe that launches an external .msi, if the prerequisite file is not in the specified location, a compile error occurs. Previously, an error did not occur.
42049: If a feature had an XML file with dynamic content configured, the XML modifications only ran during the initial install. If a feature was added later through maintenance (or advertisement) the XML configuration did not occur. This has been fixed.
42971: Fixed a problem that prevented all network computers from being listed when adding custom merge module directories during the Add Merge Module wizard.
43035: Fixed a problem that caused missing rows in the _Validation table.
43340: Fixed a problem that caused a compile error when the Cab Options was set to Quickest on the Media page.
43416: With OLE Automation, you could not compile a project file if the option Update installation as files are added or removed from source directory was selected when a directory was added to the installation and then changes were subsequently made to the source files in that directory. This has been fixed.
43584, 51403: The option to "Execute Install method" (on the File Details Dialog > Assembly tab) was using the latest version of installutil.exe found on the destination computer. If an assembly was associated with the .NET Framework version 1.1, and the .NET Framework 1.1 and 2.0 were both on the computer, the installutil.exe from 2.0 was used. This resulted in assemblies that were not registered properly. Now, every assembly in an installation is scanned and its associated version of .NET Framework is stored in a property. At run time, the appropriate version of installutil.exe is used for each assembly.
43736: (Visual Studio integrated editor.) Fixed a problem that caused dependency files that were supposed to be installed to the GAC to be installed to the root of the C drive.
44297: On computers running Windows XP, .cab and .zip files did not appear on the Files page. This has been fixed.
44312: The tools for importing Visual Basic, Visual C#, or Visual J# projects only support Visual Studio or Visual Basic 2003 or earlier. To work with projects that were created with Visual Studio or Visual Basic 2005 or later, open the project in Visual Studio .NET and create the installation in the Visual Studio integrated editor.
44659: Properties that were set on the Release Settings page were reset to the default values for non-Default languages. This has been fixed. However, if a property has a different value in another language, changing the property on the Release Settings page does not override it. Example: If a property has a value of 0 in the Default language and a value of 5 in German, and you change the value to 12 on the Release Settings page, the value in the German .MSI will be 5.
44747: If you used a restricted property in an upgrade and then deleted the upgrade setting, the property was no longer restricted. This has been fixed.
44748: Property values associated with check boxes did not update in the Debugger for Windows Installer when the checkbox was unmarked. This has been fixed.
45431: In MSI Script, the Download File From Internet action caused installations to crash on Windows 9x computers. This has been fixed.
45705: The Wise Next Dialog script incremented for each click of the Next button and skipped that many dialogs when the installation proceeded. This has been fixed.
45986, 46020, 47310: Fixed a problem that caused compiled .MSIs to be missing information in the Version column of the File table.
46021: On the Feature Details dialog, selecting Disallow Advertising from the Advertising drop-down list while the Disable advertising if not supported by OS checkbox was marked caused an error in the Feature table Attribute column. This has been fixed.
46212: (Requires a repository connection.) The Resolve Conflicts wizard within Windows Installer Editor did not show conflicts for non-binary files. This has been fixed.
46243: Fixed a problem that caused the processorArchitecture attribute to be missing for a file that was added to the GAC (Global Assembly Cache).
46346, 50591: Fixed a problem that caused an error when the same merge module was added to multiple features.
47093: When you added a custom prerequisite (Prerequisites Page > Add Button > Prerequisite) to an installation that was supposed to be digitally signed, the digital signature did not appear after compiling. This has been fixed.
47618: If a server application installation included a SQL Server Connection dialog and was installed on a server with SQL Server 2005, the SQL Server Name drop-down on the SQL Server Browse dialog did not display SQL Server 2005. This has been fixed as long as the SQL Server is configured correctly.
47712: In Installation Expert > Prerequisites page, if you select the option to add the .NET Framework runtime to an installation, a new checkbox is enabled: Show Microsoft .NET End-User License Agreement. Normally, the end user license agreement (EULA) for the .NET Framework is suppressed during installation. Mark this checkbox to override the suppression and have the EULA appear to the end user during installation.
48010: Fixed a problem with OLE Automation that caused an error when attempting to access WFWIProject.Version property.
48327: If you created a default directory path for an installation from the Default Directory field on the Product Details page, it would not retain that directory once you clicked away from the page. This has been fixed.
48574: The Sequence column of the File table only incremented to 32767. Therefore, when a merge module contained more than 32767 files, the File table sequence ended. This has been fixed.
48765: In a WebDeploy installation, when you do not specify a download path to the msiexec or .NET framework .EXEs, the prerequisite .EXEs are supposed to be compiled into the WebDeploy .EXE. This was not working in a previous release but has been fixed.
48971: The _WiseDebugMode property, which is used to debug a Call Custom DLL custom action, was not compatible with Visual Studio 7.0 and later. This has been fixed.
50188: If you created a Web application with a virtual directory, the ASPNET_USER property was not populated on computers that had ASP .NET 2.0 installed and were running Windows 2000 or Windows XP. This has been fixed.
50270: If you added a public assembly to the Global Assembly Cache folder on the Files page and marked Generate native-code version during installation for this file on the Assembly tab of the File Details dialog, the installation would end prematurely when installed on a computer with .NET Framework. This has been fixed.
51323: On the INI File Details dialog, you can enter a Windows Installer property to define a section name. This was not working but has been fixed.
51513: Using the command line option to compile a specific release (/c=release name) did not produce a compile.log. This has been fixed.
51852: The DeleteKeyRow macro function caused a crash in WfWI.exe if the target row did not exist. This has been fixed.
52225: Windows Installer Editor has been updated to support the installation of satellite assemblies to the GAC. On the File Details dialog > Assembly tab, in the Assembly Attributes section, you can define the assembly's culture attribute to better differentiate the multiple assembly versions.
52328: (Visual Studio integrated editor only.) Adding a .NET assembly that contained circular dependencies caused Windows Installer Editor to hang if the option to scan dependencies was enabled. Windows Installer Editor has been updated to break out of the infinite recursion.
52488: When files were added using wildcards specified with a WisePathVariable, UNC path, or mapped drive, short filenames were not created. This caused validation errors. It has been fixed.
52974: Viewing the File Details dialog > Dynamic Content tab for certain .XML files caused a crash. This has been fixed.
Back to Contents
New names for WiseScript tools.
Documentation. In Wise Installation Studio, the WiseScript Package Editor documentation (.CHM and .PDF) covers both WiseScript Package Editor and WiseScript Editor. Some of the information in the documentation does not apply to WiseScript Editor.
Expanded script actions. Previously, certain WiseScript-based editors contained a limited set of script actions. Now, all possible WiseScript actions are available in all editors. This lets you open any WiseScript in any WiseScript-based editor without errors. However, as always, a WiseScript will run only in an environment that supports all the actions in the script. Example: The "Get Windows Installer Property" action will not work in a script that runs outside of a Windows Installer installation.
Additional Installation Expert pages. (WiseScript Package Editor only.) The following Installation Expert pages, which previously were available only in the Wise Installation System product, have been added to WiseScript Package Editor:
Mobile device support in WiseScript. The Win CE-related pages in Installation Expert have been removed and replaced by the new Install Windows Mobile Application script action. This action adds mobile device support for the Microsoft® Windows Mobile 5.0 platform for Pocket PC and Smartphone devices. Use it to configure a WiseScript to install files that support a Windows Mobile device application. Each action line represents one mobile device application; you can enter multiple .cab files per action. When you compile the WiseScript, the .cab files are compiled into the resulting .exe. Also, an .ini file that describes the .cab files is created and included in the compiled .exe.
VBScripts in WiseScripts. The new Execute VBScript action lets you add VBScript scripts to a WiseScript. When you add a VBScript, a tab for that script appears at the bottom of the Installation Script pane. When you click this tab, the VBScript window appears, where you can create and edit VBScripts. The Execute VBScript action lets you use all the scripting capabilities of VBScript such as arrays and subfunctions. It can also save you time because you can use VBscripts that others have created. The WiseScript and VBScript interact so you can set a variable in either script and then use that variable in the other script. The VBScript window has a Call COM Object action that facilitates creating scripts to call objects. If an object is registered on your computer and has a ProgID, the Call COM Object will capture that ID for you. For many objects, this action will also add the object to a right-click menu Objects List and create a List Properties/Methods drop-down list for the object. Two sample scripts (MakeWebDir.wse and SetGetVariable.wse) that illustrate executing a VBScript in a WiseScript are in the WiseScript Editor\Samples directory.
Upgraded Actions list. In Script Editor, the Standard and Custom tabs have been replaced with an All Items and Custom title bar. When you click a title bar, it displays that group's list of actions. You can add additional groups and add any actions that appear in the All Items group to the Custom group or any group that you add.
WiseScript portable project. You can create a portable WiseScript project. This portable project file is a self-extracting .EXE that contains all of the files in the script including the source files. You can add password protection to this portable project. Select File menu > Create Project Package.
Script actions for Web sites. Two new Web-related script actions have been added to Script Editor. The Create Virtual Directory script action lets you create new IIS Web sites or virtual directories with a WiseScript. The Set Web Permissions script action lets you set permissions on an existing IIS virtual directory. You can use this action to set the permissions on virtual directories that you create with the Create Virtual Directory script action.
Script actions for SVS. New SVS (Software Virtualization Solution) specific script actions have been added to the Script Editor. You can use these script actions to create a WiseScript that creates, edits, or manipulates a virtual software layer. All of these script actions are grouped under the SVS Items title bar.
Language support. (WiseScript Package Editor only.) Default translations for French, German, Italian, and Spanish have been added to WiseScript Package Editor. These translations include strings for installation messages and dialogs. This lets you easily create an installation that displays its user interface in one of those languages. To do so, in Installation Expert > Languages page, add the language and mark its checkbox. When an end user runs an installation that supports multiple languages, the Select Language dialog appears first, and prompts the user to select a language. Subsequent installation messages and dialogs appear in the selected language.
Customizable page groups. The ability to customize Installation Expert page groups has been added to WiseScript Package Editor. Select Pages menu > Customize.
Get the operating system's processor type. An option has been added to the Get System Information script action—Is OS 64 Bit—to determine whether the destination computer is running a 64-bit operating system. The value of the variable you specify is set to 1 if the computer is running a 64-bit operating system, and 0 if not.
Back to Contents
Note: The numbers that precede some items below are issue tracking numbers.
35662: When the "Delete files in use" option was marked on the Uninstall page, the uninstall would remove the files but leave an empty directory. This has been fixed.
35760: Fixed a problem that caused the Install File(s) action to change the date/time stamp of a file when installing to a network share in Windows 2003.
36032: During installation of a WiseScript .EXE, if a file in the installation is in use, the user is prompted to retry, ignore, or abort the installation. When the file in use was on a network and the end user chose to ignore or abort the installation, the file that was in use was deleted. This has been fixed.
37637: When an Exit Installation action was included in a WiseScript .EXE, and the Failure option was marked under "Install Status MIF", custom actions in the Exit script did not execute. This has been fixed.
42168: When a WiseScript contained two Check HTTP Connection actions, and the first one failed, the second one would not execute. This has been fixed.
42361: Fixed a problem that caused the Install File(s) action to return an incorrect exit code on failure.
42827: Previously, a WiseScript would not create an .INI file if the directory did not exist. This has been fixed.
45081: Resolved a performance issue that occurred when running WebDeploy installations.
45219: Fixed a problem that caused the Register Fonts action to hang the installation on some NT-based computers.
46633: On the dialog for the Check If File/Dir Exists script action, you can specify the full path to a .DLL to check for the .DLL in the specified path. If you enter the .DLL file name without the path, the script action finds any .DLL by that name.
46776: Deleting a block of script that contained more than one Include Script action caused a crash. This has been fixed.
47138: Adding more than 1024 items in the Custom Dialog Script Editor caused a crash. This has been fixed.
47139: Nested If statements were not handled correctly in the Custom Dialog Script Editor. This has been fixed.
47147: File Associations did not support long file names. This has been fixed.
47154: Fixed a problem
that caused files of the same version to be overwritten, even
when the Replacement Options settings (on the Install File
Settings dialog) were set to Older.
47156: Fixed a problem that caused the Copy Local File action to improperly prompt for a reboot.
52459: Fixed a buffer problem that caused a WiseScript .EXE to crash if it tried to append to a large Multi-String registry key.
Back to Contents
To request a new product feature, enter a request on our Web site at: www.wise.com/support_Feature.asp. Although we always welcome your product suggestions and feature requests, we might not be able to accommodate all of them in the current product cycle. If not, we will record them and consider them for a future release.
Wise Solutions, Inc.,
a wholly owned subsidiary of Altiris, Inc.
47911 Halyard Drive; Plymouth, Michigan 48170 USA
Sales: +1 800 554 8565 (+1 734 456 2100 international)
Technical Support: +1 734 456 2600
For support options, refer to the Support area of our Web site at www.wise.com/support.asp.
Copyright 2006 by Wise Solutions, Inc. All rights reserved.