Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Table of Contents

Quick Links

Download this manual

Windows Installer Editor Reference

Table of Contents

Troubleshooting

Summary of Contents for Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0

Page 1 Windows Installer Editor Reference...
Page 2 Copyright © 2010 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
Page 3: Technical Support
Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about Symantec’s support offerings, you can visit our web site at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.
Page 4 Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/ Customer service Customer service information is available at the following URL: www.symantec.com/business/support/...
Page 5 Consulting Symantec Consulting Services provide on-site technical Services expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.
Page 6: Table Of Contents
Contents Technical Support ............3 Chapter 1: Introduction .
Page 7 Using Component Rules to Align GUIDs in an Upgrade ......59 Customizing Component Rules ..........60 Adding and Editing Component Rules .
Page 8 Adding a New Feature ........... 114 Configuring a Feature Using Its Drop-Down List .
Page 9 Adding an Environment Variable..........176 Adding File Associations .
Page 10 Tips for Creating an Efficient WebDeploy Installation ......233 Creating a WebDeploy Installation ......... . 233 Uploading a WebDeploy Installation to the Web .
Page 11 Creating a Language Transform ..........290 Sharing Language Settings Between Releases .
Page 12 Creating a Patch File ........... . 337 Specifying Previous Versions for Patches .
Page 13 Setting Transform Details ..........386 Applying a Transform to an Installation .
Page 14 Chapter 16: Using Conditions and Properties ....... . 437 Conditions ............. . 437 Where Can You Use Conditions? .
Page 15 Creating, Editing, and Running a Macro........483 Events That Can Trigger a Macro .
Page 16 Call VBScript From Embedded Code ......... 521 Call VBScript From Installation .
Page 17: Chapter 1: Introduction
Chapter 1 Introduction This chapter includes the following topics: About Windows Installer Editor on page 17 Starting the Software on page 18 The Product Interface on page 18 About Visual Studio Integration on page 19 Using Installation Expert on page 20 Using the Task List on page 26 Using a Wise Package Studio Repository...
Page 18: Starting The Software
Introduction Starting the Software To start the software Select Start menu > Programs > Symantec > Wise Installation Studio > Windows Installer Editor. Select File menu > New. The New Installation File dialog box appears. Complete the dialog box: In the Categories list, click Predefined Templates.
Page 19: About Visual Studio Integration
Introduction MSI Script MSI Script provides a powerful yet easy-to-use environment for editing Windows Installer installation sequences. A sequence is a set of actions that are performed during a particular type of installation. MSI Script is easy to work with even if you are not familiar with the underlying Windows Installer technology.
Page 20: Using Installation Expert
Introduction In the Visual Studio integrated editor, installations synchronize automatically with the other projects in the solution. Example: adding .EXEs, .DLLs, .OCXs, and assemblies to the solution adds them to the installation. Installation meta data fields (examples: application name, version, manufacturer, and default directory) are populated using data from the Visual Studio solution.
Page 21 Introduction Installation Expert window in Windows Installer Editor Page Views Page Area Page Groups View Navigation Compile and Test Page Views Use the Page Views drop-down list to select a page view, which is a set of Installation Expert page groups and pages. About Page Views on page 22 and Customizing Page Views...
Page 22: About Page Views
Introduction Compiling and Testing Compile, Test, Debug, and Run buttons test and compile the installation. In Visual Studio: These buttons are not available, but the same functionality is available through menu commands.) See also: Using the Current Release Drop-Down List on page 25 Using the Current Feature Drop-Down List on page 24...
Page 23: Customizing Page Views
Introduction Creating and Editing Installation Templates on page 54. When you use a template to create an installation, the default page view is the page view that was displayed when the template was created. If the template’s default page view is a custom page view, you can customize it. Customizing Page Views on page 23.
Page 24: Using The Current Feature Drop-Down List
Introduction To create a page view From the Page Views drop-down list in Installation Expert, select <New View...>. The Enter Name dialog box appears. Enter a name for the page view. To create an access key for the name, type & (ampersand) before a letter in the name.
Page 25: Using The Current Release Drop-Down List
Introduction Current Feature drop-down list Example: Suppose you have three features, and each feature requires different registry entries. On the Registry page, you select the first feature from Current Feature, create its registry entries, select the second feature in the list, create its registry entries, and so on.
Page 26: Using The Task List
Introduction Using Installation Expert on page 20 Using the Current Feature Drop-Down List on page 24 Using the Task List When Windows Installer Editor encounters installation issues that could cause problems, it displays them in the Task List. You can manually display or hide the Task List from the View menu.
Page 27: Filtering The Task List
Introduction Task List Icons The following icons help you quickly identify the types of tasks in the Task List: An error that will cause incorrect behavior and must be fixed Validation issues found by Package Validation Validating a Package on page 404. A task you created If you have a repository connection, this icon also appears with a task that reminds you to add the package meta data to the...
Page 28: Finding Table Errors From The Task List
Introduction User-Defined Tasks that you have created. When you set a filter, it is in effect until you change it. However, when you encounter installation issues, the filter is reset to All so installation issues can be displayed. Finding Table Errors From the Task List If a task is associated with a table, you can access that table directly from the Task List, which helps you discover the problem that caused the issue.
Page 29: Using A Wise Package Studio Repository
Introduction Click anywhere outside the box that contains the new task. The task is added to the Task List and appears in the Description column. User- defined tasks do not use the Tables column. See also: Using the Task List on page 26 Using a Wise Package Studio Repository Requires a repository connection.
Page 30: About The Share Point Directory
Introduction Custom actions Dialog boxes and dialog box themes Languages Merge modules Installation templates Validation modules Other resources (bitmaps and icons that are used in installations) Setting Repository Options on page 50. Add a file to an installation from the Wise Software Repository, to ensure that you use the correct versions of file resources in applications you develop.
Page 31: Generating Shared Resource Reports
Introduction Deleting Files From the Share Point Directory Warning Do not edit or delete the contents of the share point directory or its subdirectories outside Windows Installer Editor or other Wise tools. Doing so will cause problems in Wise Package Studio and can result in loss of data. A common question is “Can I clean up the share point by deleting unused source files?”...
Page 32: Installation Resources And Their Locations
Introduction From Group, select the group that contains the packages to compare this installation to. Click Next. The report is generated and displayed in the Shared Files Report or Shared Registry Report dialog box. You can save the or print the report from this dialog box. Saving to HTML is available only on computers that contain MSXML.DLL, which is included in Internet Explorer 5.x and higher.
Page 33: Generating Package Contents Reports
Introduction Directory Contents Templates Macros and additional template files that are used by Package Distribution. Templates\Dialogs The Wise Standard.MSI that provides information that is used by the New Dialog Wizard to add a new dialog box to an installation. Templates\File Templates that are used to create a new installation.
Page 34: Downloading Redistributable Files
Introduction Use a report’s table of contents to quickly access information about a specific type of resource. You can print the report or save it as an HTML or XML file. Downloading Redistributable Files The Download Redistributables wizard, available from the Help menu, lets you obtain merge modules, Windows Installer runtime installers, and .NET Framework runtime installers.
Page 35: Downloading Redistributables From Other Vendors' Web Sites
Introduction In the Modules Available or Versions Available list, mark one or more check boxes for the redistributables to download. Click Next. If you chose to download any merge modules, the Target Location dialog box appears, where you specify merge modules’ download location; otherwise the download starts and you can skip the next step.
Page 36: Product Documentation
The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. To access the release notes, select Release Notes from the Symantec program group on the Windows Start menu. Windows Installer Editor Reference...
Page 37: Chapter 2: Setting Up
Chapter 2 Setting Up This chapter includes the following topics: How you can set up Windows Installer Editor on page 37 Setting Options on page 37 Creating and Editing Installation Templates on page 54 Component Rules on page 57 Connecting to a Wise Software Repository on page 65 How you can set up Windows Installer Editor Before you create and edit installations, set up Windows Installer Editor to reflect your...
Page 38: Setting General Options
Setting Up Setting .NET Assembly Options on page 40 Setting Advertising Options on page 41 Setting Digital Signature Options on page 43 Setting ExpressBuild Options on page 44 Setting Installation Expert Options on page 47 Setting Merge Module Directories on page 48 Activating Suppressed Prompts on page 49 Setting Repository Options...
Page 39 Setting Up Add custom actions for predefined folders in merge modules This affects the merging of merge modules that place files in predefined directories, such as \Windows, \System32, and so on. Mark this to have the merge emulate the behavior of the Microsoft merge tool, mergemod.dll, which uses custom actions to handle predefined directories.
Page 40: Setting .Net Assembly Options
Setting Up Refresh Projects Integrated with Visual Studio .NET This option appears only if Microsoft Visual Studio is installed. When you open a project that has been integrated with Visual Studio, this option causes the Visual Studio solution to be rebuilt so that this installation has the most recent files. “Integrated”...
Page 41: Setting Advertising Options
Setting Up Assembly Scanning Options The scanning options are available only if the .NET Framework is installed on your computer. Scan Dependencies Specify how dependency assemblies are added to an installation. You can add them manually or have Windows Installer Editor scan the assembly manifest for dependencies and add them automatically.
Page 42 Setting Up To set options: Select Tools menu > Options and click the Advertising tab. (In Visual Studio: Tools menu > Options > Wise Options > Advertising.) Complete the tab. Advertising Setting Select one of the “scan” options to have Windows Installer Editor inspect your computer’s registry and the files in the installation and automatically add Windows Installer advertising information for the files that you add to the installation.
Page 43: Setting Digital Signature Options
Setting Up .DLL files. The .DLL or .OCX may require certain files to be installed already in order to self-register properly. Scanning the advertising information into the advertising tables is recommended over self-registration. Default to rescan advertising for new components If the advertising information contained in your files might change during the development process, mark this to scan the advertising information and update the installation every time you compile.
Page 44: About Expressbuild
Setting Up See also: Adding a Digital Signature to a Patch on page 341 Adding a Digital Signature to an Installation on page 262 Setting Options on page 37 About ExpressBuild Note For multi-processor compile to occur using distributed computers, all source files of the installation must be on a shared drive and must be specified in the installation with UNC paths.
Page 45: How Expressbuild Groups Work
Setting Up prevented from doing so. If you mark Allow My Computer to Build for Others, your computer is immediately available to assist in compiles being performed on other computers. Build Using Multiple Local Processors Mark this to have multiple processors within this computer help process compiles. The processors on this computer can be physical or virtual processors.
Page 46: Requirements For Using Expressbuild
Setting Up for Others check box. (In Visual Studio: Tools menu > Options > Wise Options > Prompts.) Then enter the group name of the build group your computer will build for. Do this on each computer that will share processing as part of a single build group. When you click OK on the Options dialog box, the WiseExpressBuild.exe immediately begins running on your computer, with its icon showing in the system tray area of your taskbar.
Page 47: Setting Installation Expert Options
Setting Up browse under the My Computer icon, the path will not be referenced in UNC notation. See also: About ExpressBuild on page 44 Setting ExpressBuild Options on page 44 How ExpressBuild Groups Work on page 45 Setting Installation Expert Options You can set options that control the behavior of Installation Expert.
Page 48: Setting Merge Module Directories
Setting Up Expand all features on Features page Display Feature title instead of name on Features page Display hidden features on Features page These check boxes determine how features are displayed on the Features page. You can override these settings using the right-click menu on that page. Display the page view associated with a project when a project is opened Mark this to display an installation project’s default page view when the installation opens.
Page 49: Activating Suppressed Prompts
Setting Up If you have a repository connection, you can change this to the Merge Modules subdirectory of the share point directory. To exclude the merge modules in the default directory from the list, mark Do not show merge modules from the Default Merge Module Directory. Read Merge Modules List From Software Manager Database (Requires a repository connection.) Mark this to include merge modules from the Software Manager database on the Select Merge Module dialog box that appears...
Page 50: Setting Repository Options
Setting Up Setting Repository Options Requires a repository connection. Use the Repository tab on the Wise Options dialog box to specify the directories that contain the resources that are used to create and edit Windows Installer installations. Typically, you will use the default locations, but you can set alternate locations for specific resources.
Page 51: Setting Source Control Options
Setting Up Dialogs Specify the location of the Wise Standard.MSI that contains information that the New Dialog Wizard uses to add a new dialog box to an installation. Languages Specify the location of language resource files. Resources Specify the location of the bitmaps and icons that are used in installations. Templates Specify the location of installation templates and WfWI macros.
Page 52: Setting Visual Studio Options
Setting Up Note If the following options do not appear on the Source Control tab, you probably don’t have a source code control system on your computer. It could also be that your SCCS is unrecognized or that there are communications problems between the SCCS server and your computer.
Page 53 Setting Up Projects Options To override these defaults for individual installations, or to change them for existing installations, edit the Projects page of the installation project settings. Entering Project Settings on page 85. Scan Method Each time you load, save, or build an installation project or change its settings, Windows Installer Editor can scan the other projects in the solution for new files to add to the installation.
Page 54: Setting Wildcard Groups
Setting Up Setting Wildcard Groups On the Wildcard Groups tab, you can create groups of wildcards so you don’t have to type multiple wildcards repeatedly. On the Files and Web Files pages in Installation Expert, you use the wildcard groups when you add directory contents.
Page 55 Setting Up Warning Editing predefined templates is not recommended, because they might be overwritten during upgrades. Instead, save customized templates with different names, or make copies of the predefined templates and edit the copies. Template Location in the Wise Editor Templates are in the Templates\File subdirectory of the Windows Installer Editor installation directory.
Page 56 Setting Up Name the file and save it in the Templates directory as a .WSI, .MSI, .WSM, or .MSM. When you save the template, a page view is created with the same name and is listed in the Page Views drop-down list. However, when you use the template to create an installation, the default page view is the page view that was displayed when the template was created.
Page 57: Component Rules
Setting Up when the template was created. If the template’s default page view is a custom page view, you can customize it. Customizing Page Views on page 23. To test the new template, do the following: If you saved the template in the Templates\Project directory, select File menu > New >...
Page 58: About Component Rules
Setting Up See also: About Component Rules on page 58 Selecting a Component Rule Set on page 58 Using Component Rules to Align GUIDs in an Upgrade on page 59 About Component Rules A component rule set manages components that are added to installations. A rule set is a collection of rules.
Page 59: Using Component Rules To Align Guids In An Upgrade
Setting Up In the Component Key Values section, select an option from the Default list to determine the naming convention for new components. If the rule set you use specifies the component naming under certain conditions, the naming convention you specify here will be overridden when those conditions are met. Set component key to a named Base Select this to name new components with specified text plus an incremental number.
Page 60: Customizing Component Rules
Setting Up previous .MSI is matched and the component key is set to match the previous version. All new resources you add to the upgrade installation will be checked against the previous installations. To ensure that all resources you add to an upgrade installation are aligned with previous versions, specify the previous installation versions before adding any resources to the installation.
Page 61 Setting Up See Organizing Applications into Components and Changing the Component Code in the Windows Installer SDK Help. To add a new component rule set Select Component Rules menu > Customize. In Visual Studio: Project menu > Component Rules > Customize. The Component Rules Manager dialog box appears, listing the predefined rule sets and custom rule sets you have created.
Page 62: Adding And Editing Component Rules
Setting Up Note If you selected a predefined rule set, all the buttons on the Customize Components Rules dialog box are unavailable because the predefined rule sets are read-only. However, you can use this dialog box to view the rules in a predefined rule set.
Page 63: Microsoft Best Practices Component Rule Set
Setting Up When there are no conditions for performing the action(s) in this rule, select the condition Always perform associated action. As you mark check boxes, the conditions appear in the Rule description list. If you select a condition that is incompatible with a condition you have already selected, the first condition you selected is removed from the list.
Page 64 Setting Up Match components in previous versions of the .MSI If the keypath resource matches a resource in the previous .MSI list, match the component layout of the previous .MSI and set the component key to match the previous version. Add all executable files to their own components If the added resource is a 32-bit executable file (.DLL, .OCX, or .EXE), create a new component.
Page 65: One File Per Component Rule Set
Setting Up One File Per Component Rule Set When you use this predefined rule set, each file you add to the installation becomes its own component. If an added resource does not meet the conditions in a rule, the next rule is evaluated for that resource.
Page 66 Future releases of Wise Installation Studio might require an upgrade of Wise Package Studio and the repository. To connect Windows Installer Editor to a Wise Software Repository Select Start > Programs > Symantec > Wise Installation Studio > Repository Client Manager. The Repository Client Manager dialog box appears.
Page 67: Chapter 3: Working With Wise Installation Files
Chapter 3 Working With Wise Installation Files This chapter includes the following topics: Before You Create an Installation on page 67 File Types on page 68 Project Files and Database Files on page 69 Target Platforms: 32-bit and 64-bit on page 70 Starting a New Installation (page 78) Options for New Installations...
Page 68: File Types
Working With Wise Installation Files The application’s system requirements in as much detail as possible. Consider not only memory and disk requirements, but also the minimum screen depth and resolution, and the minimum required version of the operating system. Any custom graphics, referred to as billboards, that should be displayed during installation.
Page 69: Project Files And Database Files
Working With Wise Installation Files Extension Description .MSP Windows Installer patch, which updates an existing installed application. Patches contain only the differences between the old and new versions of an application. Create a patch with the Patch Creation tool, which creates an .MSP file that you distribute to end users.
Page 70: Target Platforms: 32-Bit And 64-Bit
Working With Wise Installation Files If you work in a .WSI or .WSM If you work in an .MSI or .MSM (Wise project) (Windows Installer database) How are installation Externally. The project contains paths to Inside the database file. Files are files and paths stored? the installation files.
Page 71: How To Specify The Target Platform
Working With Wise Installation Files You cannot test, run, or debug a 64-bit installation on a 32-bit computer. See: How to Specify the Target Platform on page 71 What’s Different in a 64-bit Installation? on page 72 32-bit Applications on 64-bit Computers on page 73 Guidelines for Creating Platform-Specific Installations on page 74...
Page 72: What's Different In A 64-Bit Installation
Working With Wise Installation Files Component Details dialog box To display this dialog box, select Setup Editor > Components tab, right-click a component, and select Details. The 64-bit component check box designates a component as 64-bit. This is marked when you add 64-bit .EXE and .DLL files or 64-bit registry keys. If this is not marked, the component is registered as a 32-bit component.
Page 73: 32-Bit Applications On 64-Bit Computers
Working With Wise Installation Files System Search page The Read Registry Value dialog box, which you access from the System Search page, contains a check box that lets you include 64-bit components in a registry value search. Searching For a Registry Value on page 196.
Page 74: Guidelines For Creating Platform-Specific Installations
Working With Wise Installation Files Resource Place 32-bit versions in Place 64-bit versions in Operating system components Windows\SysWOW64 directory Windows\System32 directory and shared libraries Registry keys Do one of the following: Do one of the following: Place the keys in the 32- Place the keys in the 62-bit registry view.
Page 75: Creating Multiple, Platform-Specific Installations From One Project File
Working With Wise Installation Files 64-bit Installations That Contain Some 32-bit Components Select the appropriate target platform for each feature, and add the correct type of component to each one. Do not add a 64-bit component to a 32-bit feature, and vice versa, because it will never be installed.
Page 76 Working With Wise Installation Files Organize the project by component. This method results in fewer features and possibly less duplication. However, in a large installation, it might be less efficient to have to assign a target platform to each component. To organize a mixed-platform project by feature On the New Installation File dialog box, select x64 as the target platform.
Page 77 Working With Wise Installation Files Graphic64.msi, which installs both 32-bit and 64-components and runs on x64 platforms only. Its Template Summary property is set to x64. To organize a mixed-platform project by component On the Features page, create a single set of features and set their target platform to All Processors.
Page 78: Defining The Installdir Property In A Mixed-Platform Installation
84. To start a new installation in the Wise editor Select Start menu > Programs > Symantec > Wise Installation Studio > Windows Installer Editor. The New Installation File dialog box appears. If it does not appear, select File menu >...
Page 79: About Standard User Installations
Working With Wise Installation Files In the Categories list, click Predefined Templates. In the Templates/Tools list, click the Windows Application icon. A Windows Application installation is a standard installation intended for a Windows computer or server. In the File type section, specify the type of file to create: Create an .MSI (Windows Installer database), which is a distributable installation.
Page 80: Creating An Installation For Standard Users
Working With Wise Installation Files On the Files page, a warning message appears when you try to add a file to a protected area. On the Registry page, a warning message appears when you try to add a registry key to a protected area. The DisableUAP property is set, which hides the option to install for all users or the current user on the installation’s User Information dialog box.
Page 81 Working With Wise Installation Files the other projects in the solution, additions or changes you make in the other projects can be added to the installation automatically. See How the Installation Integrates With the Solution on page 90. Each Visual Studio installation project contains settings that control how it interacts with other projects in the solution.
Page 82: Creating A Stand-Alone Installation
Working With Wise Installation Files Click Finish. An installation project is created in the location you specified and is listed in Solution Explorer. A corresponding .WSPROJ file (Visual Studio project) is created in the same location. Double-click the .WSI file in Solution Explorer. The installation opens.
Page 83: Creating A Device Driver Installation
Working With Wise Installation Files Starting a New Installation on page 78 Creating a Device Driver Installation You can create an installation that supports Microsoft Driver Install Frameworks (DIFx). Microsoft created the Driver Install Frameworks to significantly improve the quality of device driver installations.
Page 84: Options For New Installations
Working With Wise Installation Files The driver package’s .INF file must be the first file added to this directory so that it becomes the key path of the component. Add the other files that make up the driver package to the same directory that contains the .INF file.
Page 85: Entering Project Settings
Working With Wise Installation Files Server Application Creates an installation intended to be run on Microsoft IIS, with an additional dialog box for recording logon information. Obtaining Logon Information From a Dialog on page 475. Windows Mobile Opens the Windows Mobile wizard, which lets you add Windows Mobile .CAB files to a desktop installation.
Page 86: Overview Page
Working With Wise Installation Files To access project settings: Do one of the following: While creating a new installation project, select Setup Wizard on the New Project dialog box. Creating an Installation Within a Solution on page 80. The Wise Setup Wizard dialog box appears. Available pages are: Overview, Project Type, Projects, and Main Project.
Page 87: Projects Page
Working With Wise Installation Files Web Application or Web Service Create a standard Windows Installer installation (.WSI). This has options preconfigured to enable it to be installed to a Microsoft Internet Information Server. About Web Installations on page 266. Server Application Create a standard Windows Installer installation (.WSI).
Page 88: Main Project Page
Working With Wise Installation Files Prompt when any files are detected This is the highest level of prompting. Like the previous option, the prompt appears during save, build, or compile when there are new files. Also, if you previously excluded files by clearing their check boxes, you’ll be prompted to confirm that those files should be excluded.
Page 89: Pre-Build Event
Working With Wise Installation Files Creating an Installation Within a Solution on page 80 Entering Project Settings on page 85 Pre-build Event Visual Studio integrated editor only. The Pre-build Event page lets you add to a project anything that is needed before the build occurs.
Page 90: How The Installation Integrates With The Solution
Working With Wise Installation Files Source Files Include all source code files in the project. Content Files Include all files marked as content within the project, that is, files that are not compiled but are meant to be distributed with the application. Examples: HTML, ASP, and ASPX files.
Page 91: Scanning The Solution For New Files
Working With Wise Installation Files When you add a new project to the solution, its outputs are added to the installation. To exclude a project from the installation, or to change how the installation project integrates with the solution, edit the installation’s project settings. Entering Project Settings on page 85.
Page 92: Opening An Installation Package
Working With Wise Installation Files Add and edit multiple files at once by selecting them and clicking the Properties button. On the Project Output Properties dialog box that appears, you can add a new feature and add a new directory for all of the selected files. Note In a Web installation, you can only change the destination feature.
Page 93: Comparing Windows Installer Files
Working With Wise Installation Files (Revision Control is available only in the Wise Package Studio version of Software Manager but it can affect packages that you open in Wise Installation Studio.) To open a package from a directory: Click the File System tab on the Open dialog box and navigate to a package. This is the same as the standard Windows Open dialog box.
Page 94 Working With Wise Installation Files To view differences between two Windows Installer files Open a file. Select Tools menu > Visual MSIDiff and then select an option. In Visual Studio: Project menu > Visual MSIDiff. Compare Current File to Another File The Compare Windows Installer Files dialog box appears.
Page 95: Saving An Installation As Xml
Working With Wise Installation Files Saving an Installation as XML You can save a copy of an installation (.WSI, .MSI, WSM, or .MSM) in XML format. This lets you check the XML version of the installation into a text-based source code control system (SCCS), use text-based file comparison tools to find changes, or perform analyses with XML reporting tools.
Page 96 Working With Wise Installation Files When the package path matches a package in the database If you open an installation file and the Software Manager database contains a package with the same package path, the application and package names on the Product Details page are unavailable.
Page 97: Compiling An Installation
Working With Wise Installation Files Compiling An Installation Compiling an installation compresses its files, builds .CABs if necessary, and creates the installation .MSI. Depending on the .EXE option you select on the Build Options page, compiling can also create an installation .EXE. (In Visual Studio: compiling and building do the same thing.) Multiple Releases The number and type of files that are generated depend on the settings you select on...
Page 98: Testing And Running An Installation
Working With Wise Installation Files Rebuild project name Compiles all files in the project you selected in Solution Explorer. Compile Compiles the current project or installation file. This is the only command available for installations that are not part of a Visual Studio installation. Compile Results If you are working in an .MSI or .MSM, compiling saves the file.
Page 99: Testing An Installation
Working With Wise Installation Files Testing An Installation You run an installation in test mode, which does not install files or change the system. This lets you run through the user interface and logic of an installation without making changes. To test an installation Click Test at the lower right of the main window.
Page 100 Working With Wise Installation Files To run an installation and install it on your computer Click Run at the lower right of the main window. In Visual Studio: in Solution Explorer, right-click the installation project icon and select Set as StartUp Project. Then, select Debug menu > Start Without Debugging. The additional options below are not available.) Select the type of installation from the button menu: Force Reinstall...
Page 101 This removes the layer that was previously created and creates a new one. Close Windows Installer Editor. Delete the virtual layer from the Symantec SVS applet. The name of the virtual layer is WiseTemp_ProductName where ProductName is the value of the ProductName property.
Page 102: Chapter 4: Defining An Installation Project
Chapter 4 Defining an Installation Project This chapter includes the following topics: Project Summary Page on page 102 Product Details Page on page 102 General Information Page on page 108 Add/Remove Programs Page on page 109 Features Page on page 110 Managing Binary Resources on page 121 Project Summary Page...
Page 103 Defining an Installation Project Meta Data and the Software Manager Database (Requires a repository connection.) If you define meta data fields in Software Manager, they appear on the Product Details page unless the Software Manager database cannot be found. You can edit these meta data fields on the Product Details page or in Software Manager.
Page 104 Defining an Installation Project (Visual Studio integrated editor only.) If this installation is part of a Visual Studio solution, this is pre-filled. Warning If you are releasing a newer version of your application but are not using an upgrade or patch, it is very important to enter a new version on the Product Details page.
Page 105 Defining an Installation Project Setting .NET Assembly Options on page 40. The ability to create .NET installations is supported only by Windows Installer 2.0 or later. Win 32 (non .NET) Select this if this is a standard Win32 installation without .NET assemblies. .NET Application Select this if this is a .NET installation with only .NET elements.
Page 106: Adding Meta Data To The Software Manager Database
Defining an Installation Project Adding Meta Data to the Software Manager Database Requires a repository connection. For an .MSI or .WSI, you can add to the Software Manager database the meta data that appears on the Product Details page. This lets you add package information to the Software Manager database early in the development or repackaging process.
Page 107: Incrementing The Product Version
Defining an Installation Project See also: Using a Wise Package Studio Repository on page 29 Incrementing the Product Version Windows Installer uses the version number of the application to identify the product when subsequent patches or upgrades are applied. How do you set the version number? The version number is stored in the Version field on the Product Details page.
Page 108: General Information Page
Defining an Installation Project Note When end users install your application, sometimes the installation directory defaults to the C drive, and other times it defaults to another drive. This happens because Windows Installer determines which drive has the most free space. To set the default installation directory Select Installation Expert >...
Page 109: Add/Remove Programs Page
Defining an Installation Project Keywords Enter a list of keywords that the end user can use to search for this installation in Windows Explorer. Installer Version (Read-only.) This displays the minimum Windows Installer version required on the destination computer to run this installation. This is not the version of the application.
Page 110: Features Page
Defining an Installation Project Hide remove button Mark this to disable the Remove button for your application in Add/Remove Programs. End users will not be able to uninstall the application using Add/ Remove Programs. Support Information Page The following information appears under the Support Information link in Add/ Remove Programs.
Page 111 Defining an Installation Project Setting Features for Installation Types on page 203. In an installation with multiple releases, you can deselect certain features for certain releases on the Release Settings page. Defining a Feature and Component Set for a Release on page 213.
Page 112: Strategies For Organizing Files Into Features
Defining an Installation Project On the Files page, add a file to each feature. Select the feature from the Current Feature drop-down list before adding the file. On the Dialogs page, clear the check box for Installation Type Dialog, and mark the check box for Select Feature Dialog.
Page 113 Defining an Installation Project assigned to the Core feature. Because they are siblings of the Core feature, an end user might install the text editor feature or the graphics editor feature without installing the core feature, which would break the installation. To avoid this problem, make the Core feature required;...
Page 114: Adding A New Feature
Defining an Installation Project Conditions See also: Features Page on page 110 Creating Multiple, Platform-Specific Installations from One Project File on page 75 Adding a New Feature To add a new feature Do one of the following: In Installation Expert > Features page, click the feature name under which the new feature should appear.
Page 115 Defining an Installation Project set in this drop-down list determines the default state of the feature during installation. The drop-down list provides a way to set common options quickly. The icon itself provides a visual cue that indicating which options have been set. The drop-down list options are a subset of the options that are available in the Feature Details dialog box, which you access by clicking the Details button at the right of the Features page.
Page 116: Configuring A Feature Using The Feature Details Dialog
Defining an Installation Project Hidden from user Prevent the feature from appearing to the end user on the installation’s Select Features dialog box. You can set this option in combination with any one of the other options above. (This option corresponds to setting Hidden in the Display drop- down list on the Feature Details dialog box.) See also: Features Page...
Page 117 Defining an Installation Project All Processors The feature appears for installation on any computer, regardless of the platform. 32 Bit Processors The feature appears for installation on 32-bit computers only. 64 Bit Processors The feature appears for installation on 64-bit computers only. x64 Only The feature appears for installation on computers that support the x86 architecture (including AMD64 or EM64T).
Page 118 Defining an Installation Project Note The end user’s action on the Installation Type dialog box determines the INSTALLLEVEL property. To see how this works, go to Setup Editor > Dialogs tab and click the Installation Type dialog in the list. Double-click the Typical/Complete/ Custom radio button, and you see that the end user’s choice in this radio group sets the property InstallMode.
Page 119: Using Conditions With Features
Defining an Installation Project None By default, the feature is set to be installed, not advertised. Favor Advertising By default, the feature is set to be advertised. Disallow Advertising The feature is set to be installed, not advertised, and the end user cannot change the default.
Page 120: Adding And Deleting Feature Conditions
Defining an Installation Project features are listed in the Current Feature drop-down list, which appears on all Installation Expert pages in the Feature Details page group. Just as you can specify options on a per-feature basis, you can also specify options on a per-condition basis. Options on these pages that you associate with a condition are installed only if the condition is true and the feature is installed.
Page 121: Managing Binary Resources
Defining an Installation Project Click OK on the Feature Condition dialog box. The condition appears in the Current Feature drop-down list. If you want to make file changes or other system changes on the destination computer only if this condition is true, you first select this condition from the Current Feature drop-down list.
Page 122: Adding Binary Resources
Defining an Installation Project File Name Path to the source file that contains the binary data <Unspecified> in this column indicates that the source file is not known. (Example: This is the case when an installation includes a third-party .MSI.) Unspecified entries are stored in the .MSI and cannot be updated during compile.
Page 123: Refreshing Binary Resources
Defining an Installation Project Create/update link to refresh data when file changes Mark this to update the data during compile with any modification you might have made to the source file. This also marks the check box in the Refresh column on the Resources page.
Page 124 Defining an Installation Project Managing Binary Resources on page 121 Windows Installer Editor Reference...
Page 125: Chapter 5: Assembling An Installation
Chapter 5 Assembling an Installation This chapter includes the following topics: Files or Web Files Page on page 125 Visual Studio Solution Page on page 157 Registry Page on page 161 INI Files Page on page 170 Shortcuts Page on page 172 Adding an Environment Variable on page 176 Adding File Associations...
Page 126 Assembling an Installation Files page in Windows Installer Editor Current Feature drop-down list Directories available to your Files in the computer directory selected on the left Directories to be installed on Files or the destination operations to be computer installed on the destination computer The Windows directory represents the system directory...
Page 127: When To Use The File-Related Installation Expert Pages
Assembling an Installation Delete (lower left) Remove a directory from the installation. This does not delete it from the destination computer. Details (lower left) On the Files page, use this to set NTSF permissions. On the Web Files page, use this to set all IIS-related details about the item, as well as Web-based security.
Page 128: Installation Directories
Assembling an Installation Page When to use it Web Files To create Web folders, virtual directories, and Web sites, and add files to them To add files to a Web installation About Web Installations on page 266. Visual Studio Solution To display the installation’s files in a solution- (Visual Studio integrated oriented view...
Page 129: Files Or Web Files Page Icons
Assembling an Installation Default directory If you specify the default directory on the Product Details page, it appears on the Files page followed by [INSTALLDIR]. This makes it easy to identify the installation directory. To enable or disable this option, select Show InstallDir from the right-click menu.
Page 130: Adding Files To An Installation
Assembling an Installation See also: Files or Web Files Page on page 125 Visual Studio Solution Page on page 157 Installation Directories on page 128 Adding Files to an Installation If you add the same file to multiple locations, it is considered a duplicate file entry. Creating Duplicate File Entries on page 421.
Page 131 Assembling an Installation To add files from the Features tab in Setup Editor On the Features tab, expand a feature and then expand its Combined folder. Expand the Files icon. If the Files icon does not appear, right-click and select Hide Empty Folders/Items. To add a new directory, right-click a directory and select New >...
Page 132: Adding Merge Modules Instead Of Files
Assembling an Installation Right-click and select Details (Components and Features tabs). Editing File Details on page 145. See also: Files or Web Files Page on page 125 Visual Studio Solution Page on page 157 Installation Directories on page 128 Files or Web Files Page Icons on page 129 Adding Contents of Directories to the Installation on page 134...
Page 133: Adding Files From The Wise Software Repository
Assembling an Installation Hide; Replace files with merge modules matching version Avoid seeing this dialog box in the future and always replace files with the corresponding merge modules. This turns the dialog box off for all instances in which it would normally appear. Hide;...
Page 134: Adding Contents Of Directories To The Installation
Assembling an Installation Warning If you are working in a Visual Studio solution, selecting a file outside the solution breaks the integration of the installation with the solution. When you build the solution, the outside file will not be built. Also, a source file outside the solution cannot be added to source control.
Page 135: Adding Files From Outside The Solution
Assembling an Installation Enter *.EXE for all EXE files. A ? represents any one character.) If you leave the wildcard fields blank, all files in the directory are added. Groups of wildcards appear in Include Wildcards, which you can edit. Setting Wildcard Groups on page 54.
Page 136 Assembling an Installation Solution Explorer. In addition, you cannot add those files to source control, because Visual Studio does not allow files outside a solution to be managed with source control. The Copy Source Files dialog box, which appears the first time you save or build a solution after adding files from outside the solution, lets you copy the source files to the solution directory.
Page 137: Adding .Net Assemblies To The Installation
Assembling an Installation Adding Files to an Installation on page 130 Adding .NET Assemblies to the Installation Note The ability to create .NET installations is supported only by Windows Installer 2.0 or later. When you create a .NET installation, you can use the Files or Web Files page to add .NET assemblies.
Page 138: How Assembly Dependencies Are Added To An Installation
Assembling an Installation Private directory If an assembly is private, used by only one application, install it into any installation directory, provided its path contains a maximum of 256 characters. See Private Assemblies in the Windows Installer SDK Help. See also: Files or Web Files Page on page 125 Visual Studio Solution Page...
Page 139: About Dependency Scan Exclusions
Assembling an Installation See also: How Assembly Dependencies are Added to an Installation on page 138 About Dependency Scan Exclusions When you add a .NET assembly to an installation, Windows Installer Editor can scan the assembly’s manifest for dependencies and either add the dependencies to the installation or prompt you to select the dependencies to add.
Page 140: Editing Settings For Automatic Updating
Assembling an Installation (Requires a repository connection) If you have multiple exclusion lists, they are used in the following order: If dotnetexclude.xml is on the local computer, it is used instead of the hard-coded list. If dotnetexclude.xml is on the share point directory, it becomes the primary exclusion list, which overrides any local exclusion lists and the hard-coded list.
Page 141 Assembling an Installation To edit the settings for automatic updating of a directory Select Installation Expert > Files or Web Files page. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Click the directory name in the lower-left list box and click Wildcards at the lower left of the Files or Web Files page.
Page 142: Removing A File From The Destination Computer
Assembling an Installation Windows Installer only increments the shared DLL count on a file if the file is installed and has an existing shared DLL count. If a component is installed to the Global Assembly Cache, you cannot increment the shared DLL count. Leave installed on uninstall Mark this to leave the component installed when its parent feature is uninstalled.
Page 143: Copying And Moving Files On The Destination Computer
Assembling an Installation a. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 144 Assembling an Installation To copy and move files on the destination computer Do one of the following: Select Installation Expert > Files or Web Files page. a. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 145: Editing File Details
Assembling an Installation Adding Files to an Installation on page 130 Editing File Details When you add a file to an installation, it inherits the attributes of the original file. If you edit the attributes of a file in an installation, the file reflects your edits when it is installed on the destination computer.
Page 146: Editing General File Details
Assembling an Installation Editing General File Details To edit general file details Do one of the following: In Installation Expert: On the Files or Web Files page, select one or more files and click Details. In the Visual Studio integrated editor, you also can use the Visual Studio Solution page.
Page 147: Setting Permissions For Files And Directories
Assembling an Installation File has Valid Checksum Many executable files (examples: .EXE, .OCX, .DLL, etc.) store a checksum that can be checked against actual file contents to ensure the file is not corrupted. Mark this to have file contents verified during reinstall or repair. If the verification fails, the file is assumed to be corrupted and is replaced.
Page 148: Editing Self-Registration Settings For Files
Assembling an Installation A dialog box appears with a Permissions tab. If you selected multiple files that have different permissions, you are prompted to reset the permissions to a common set when you click the Permissions tab. If you do not reset the permissions, the Permissions tab is unavailable.
Page 149: Editing Assembly Settings For Files
Assembling an Installation Use order specified below (Not available in a merge module.) Select this if this file requires that other files in the installation be registered first for it to self-register properly. This enables the Registration Order field. Registration Order This section lists files you selected for self-registration with the Use order specified below method.
Page 150: Creating A Win32 Assembly
Assembling an Installation Manifest .NET and Win32 assemblies require a manifest. Select the file that contains the manifest for this assembly. For .NET assemblies, this often is the same as the file you are editing, because most manifests are embedded in the assembly file or in one of the files in a multifile assembly.
Page 151 Assembling an Installation Create a manifest for a Win32 assembly outside Windows Installer Editor, then add the assembly and its manifest to the installation as you would any other files. On the Assembly tab of the File Details dialog box, mark it as a Win32 assembly and specify the manifest file.
Page 152: Viewing Shared File Resources
Assembling an Installation For details, search for “Windows XP visual style” in the MSDN Library (msdn.microsoft.com). Click OK, then click OK on the File Details dialog box. The manifest file is created in XML format and added to the installation with the same name as the dependent file plus “.manifest”.
Page 153: Editing Xml Files During Installation
Assembling an Installation To select a different file Warning If you are working in a Visual Studio solution, selecting a file outside the solution breaks the integration of the installation with the solution. When you build the solution, the outside file will not be built. Also, a source file outside the solution cannot be added to source control.
Page 154: Editing Difxapp Options
Assembling an Installation The Edit button becomes enabled for editable lines only after you mark Enable Dynamic Content. Select a line and click the Edit button. Not all lines are editable, only lines that have name-value attributes. (Example: <compilation defaultLanguage=”c#” />.) The Attribute Editor dialog box appears. To edit an XML attribute: Select the attribute in the top list box.
Page 155: How Self-Registration Information Is Captured
Assembling an Installation Complete the dialog box: Use DIFxApp to install this driver file When you mark this check box, the other options become enabled. They are all marked by default. Retain better-matching PnP function drivers Mark this to retain the device’s Plug and Play function driver if it is a better match for the device than the driver in the installation.
Page 156: Using Wisecomcapture.exe
Assembling an Installation Using WiseComCapture.exe. Using WiseComCapture.exe before you can scan a file’s self-registration information and add it to an installation, the file must be registered on your computer. If you prefer not to register files on your computer, you can run the scan routine as a stand-alone utility on a different computer. This utility, WiseComCapture.exe, is in the Windows Installer Editor installation directory.
Page 157: Visual Studio Solution Page
Assembling an Installation Visual Studio Solution Page Visual Studio integrated editor only. This page is available only if the installation is part of a Visual Studio solution. The Visual Studio Solution page is similar to the Files page, except: The upper-left list box displays the projects in the solution and organizes each project’s output by output groups.
Page 158 Assembling an Installation When new output files are added to the solution, they are added to the installation in the same directory as their output group, even if the output group was moved from its original directory. If you select the option to maintain an output group’s directory structure, when you add new files to the solution, they are added to the corresponding directory in the installation.
Page 159: Adding Contents Of Visual Studio Projects To The Installation
Assembling an Installation Warning When you remove an output group from the lower-right list box, all other outputs of that group are removed from the installation. Also, the check box for that output group is cleared on the Project Output page in the project settings, which excludes that group from future scans for output files.
Page 160 Assembling an Installation Items that you add to a feature are installed on the destination computer only if the feature is installed. Items that you add to a condition are installed only if the feature is installed and the condition is true. In the upper-left list box, expand a project and select the output group to add.
Page 161: Visual Studio Solution Page Icons
Assembling an Installation structure, when you add new files to the solution, they are added to the corresponding directory in the installation. Click OK. The files in the selected output group are added as specified. See also: Visual Studio Solution Page on page 157 Visual Studio Solution Page Icons on page 161...
Page 162 Assembling an Installation Registry page in a 32-bit installation Registry keys on your Registry values in the key computer. selected on the left. Registry values Registry keys to to be installed be created on on the the destination destination computer. computer.
Page 163: Adding Registry Keys
Assembling an Installation Working with the Registry page If the installation has multiple features, specify the feature you are configuring by selecting it from the Current Feature drop-down list. Use the right-click menu to expand or collapse directories, to hide or show empty directories, and to view the 32-bit or 64-bit registry.
Page 164 Assembling an Installation From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 165: Removing Registry Entries From The Destination Computer
Assembling an Installation When an installation contains both 32-bit and 64-bit components, place registry keys in the appropriate location for the platform they target. Expand the Registry icon. To add a new folder, right-click a folder and select New > Folder. Rename the new folder.
Page 166: Importing And Exporting Registry Entries
Assembling an Installation To add a remove registry operation in Setup Editor Do one of the following in Setup Editor: On the Features tab, expand a feature and then expand its Combined folder. If the Combined folder does not appear, right-click and select Hide Empty Folders/Items.
Page 167: Configuring General Registry Settings
Assembling an Installation To import a registry file Do one of the following: Select Installation Expert > Registry page. a. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 168 Assembling an Installation To configure general registry settings Do one of the following: In Installation Expert > Registry page, click Add > Key at the lower left of the page. Double-click a registry value on the Registry page in Installation Expert or on the Components or Features tab in SetUp Editor.
Page 169: Setting Permissions For Registry Keys
Assembling an Installation file name, enter a value of [#MyApp.exe].) For information about formatted text strings, see Formatted and Registry Table in the Windows Installer SDK Help. Data Type Select the type of data contained in the named value. The associated Windows API data types are in parentheses below. String (REG_SZ) Identifies the value as an expandable string.
Page 170: Viewing Shared Registry Resources
Assembling an Installation Enter or select a User name. Click OK. The domain and user names appear in the upper list box, and the list of permissions is enabled. To set permissions, mark the check boxes. You can add multiple users. Viewing Shared Registry Resources Requires a repository connection.
Page 171: Creating And Editing .Ini Files
Assembling an Installation You cannot use this page to delete part or all of an .INI file. The left list box on this page represents the directory tree of the destination computer, and the right list box contains .INI entries you add to the installation. Use the right-click menu to expand or collapse folders and to hide or show empty folders.
Page 172: Shortcuts Page
Assembling an Installation The INI File entry appears in the right list box. To edit it, double-click its name. To delete it, use the right-click menu. To create and edit an .INI file from Setup Editor On the Components or Features tab, expand a component or feature. To create a new folder for the INI file, right-click the INI Files icon or one of its subfolders and select New >...
Page 173: Adding A Shortcut To An Installation
Assembling an Installation Shortcuts for files that have associated shortcuts are created automatically if you select one of the scan advertising options from the Advertising Setting drop-down list in Wise Options. (Visual Studio integrated editor only.) If the installation is part of a Visual Studio solution, an advertised shortcut for the application is created by default.
Page 174: Editing A Shortcut Configuration
Assembling an Installation Editing a Shortcut Configuration on page 174. Shortcut Name Enter a name for the shortcut. Click Next. If you created a shortcut for a file in the installation, the Shortcut File Selection dialog box appears. Select the installation file to create a shortcut for and click Next. Note Files added under the Duplicate Files icon in the Features or Components tabs of Setup Editor do not appear because you cannot add shortcuts for duplicate files.
Page 175 Assembling an Installation Name The name of the shortcut. If the name is longer than 8.3 characters, the short (8.3) file name appears first, followed by a pipe character (|) and the long (Windows 95) file name. Target File (Read-only.) This contains the file name of the target of this file. You specified this file when you created this shortcut.
Page 176: Adding An Environment Variable
Assembling an Installation Adding an Environment Variable You can add, edit, and delete environment variables and values to be set by the operating system on the destination computer. You can add environment variables from Installation Expert or Setup Editor. To add an environment variable Do one of the following: Select Installation Expert >...
Page 177 Assembling an Installation Select Installation Expert > File Associations page. a. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 178: Determining Extension Settings
Assembling an Installation See also: Advertising Icon on page 420 Determining Extension Settings Use the Extension Details tab to determine file association settings. To determine file association settings Click the Extension Details tab on the File Associations Details dialog box. Adding File Associations on page 176.
Page 179: Selecting Mime Types
Assembling an Installation Verb Enter or select the action to be performed when the end user selects the corresponding command from the right-click menu. Command Enter the command as it should appear on the right-click menu. This entry is added to the text strings on the Languages page and can be localized.
Page 180 Assembling an Installation To add a service Select Installation Expert > Files page. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 181: Controlling Services On The Destination Computer
Assembling an Installation Login Username, Password Enter the Windows account information for the account the service is to run under. Example: .\Username or Domain\Username. Load Order Group Enter the group that this service will be a part of. Groups are loaded alphabetically at startup.
Page 182: Adding An Odbc Item
Assembling an Installation a. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 183: Setting Odbc Data Source Details
Assembling an Installation Select Installation Expert > ODBC page. a. From Current Feature, select a feature or condition. (Because any item you add must be assigned to a specific feature, you cannot add an item when All Features is selected.) Items that you add to a feature are installed on the destination computer only if the feature is installed.
Page 184: Setting Odbc Driver Details
Assembling an Installation Setting ODBC Driver Details To set ODBC driver details Access the ODBC Driver Details dialog box. Adding an ODBC Item on page 182. Complete the dialog box: Driver Name Enter a name for the driver, or click Import to import driver information from a saved driver file.
Page 185 Assembling an Installation On the Firewall Exceptions page, you can specify application files and ports to be added to the Windows Firewall exception list during installation. This adds custom actions to the installation, which add the exceptions to the Windows Firewall exception list. When your application is installed, it can accept incoming traffic and open required ports on the destination computer without end user intervention.
Page 186 Assembling an Installation The Application Selection dialog box appears and displays files in the installation with the following extensions: .EXE, .COM, or .ICD. Select a file. A file can appear in the exception list only once. The Friendly Name defaults to the file name. You can edit this information. Click Finish.
Page 187: Chapter 6: Your Installation On The Destination Computer
Chapter 6 Your Installation on the Destination Computer This chapter includes the following topics: About System Requirements on page 187 Performing a System Search on page 191 Setting Version-Specific Windows Installer Options on page 198 Setting Features for Installation Types on page 203 About System Requirements You can define system requirements for an installation in two different areas of Windows...
Page 188 Your Installation on the Destination Computer Requirements that begin with “All” or “Do not check” indicate that this requirement is not checked. Any requirement you select includes not only the requirement but also any greater value. Example: Selecting a Windows version of Windows XP lets an installation run on any computer with Windows XP or any later versions of the same operating system.
Page 189: Setting A System Requirement For Server Roles And Services
Your Installation on the Destination Computer Adding Prerequisites to a Release on page 221. SQL Server Version Use this option to check for the presence of SQL Server. By default, this value is not checked. This option is useful if you have set up this installation to configure a Microsoft SQL Server on the SQL Server Scripts page.
Page 190: Adding Roles And Services To The Server Roles And Services Dialog Box
To add server roles and services to the Server Roles and Services dialog box Access the roles.txt file and remove its Read-only attribute. By default, the file is in the Program files\Symantec\Wise\Windows Installer Editor directory. Open the roles.txt file. Below the last entry, type SVFT_ followed by the value for the server role or service.
Page 191: Setting A Requirement By Creating A Launch Condition
Your Installation on the Destination Computer The next time you open the Server Roles and Services dialog box, the options you added to the roles.txt file appear in the list of server roles and services. Setting a Requirement by Creating a Launch Condition You can use launch conditions to check system requirements on the destination computer.
Page 192: Searching For Files Or Directories
Your Installation on the Destination Computer To find a previous version of your application that wasn’t installed using Windows Installer technology. To find any files, directories, .INI files, registry entries, or components of a previous version of your application. You can specify the items to search for and then code the installation so the new version is placed in the same location as the previous one, rather than in a default location.
Page 193 Your Installation on the Destination Computer Search all fixed drives for a file Searches all permanent attached drives for the file. You determine how many levels down the search is performed by entering a search depth. This operation returns the entire path to the file. Example: C:\Program Files\Application\Application.exe.
Page 194: Searching For Items In .Ini Files
Your Installation on the Destination Computer Min. Size The file’s size must be equal or greater than this number. Leave the default value of 0 to ignore the file size. Max. Size The file’s size must be equal or less than this number. Leave the default value of 0 to ignore the file size.
Page 195 Your Installation on the Destination Computer Property Specify a property name. It will hold the result of the search, which is a file name, directory path, or other value, depending on the operation performed by the search. If you’ve already defined a new public property (all uppercase) in the Properties icon on the Product tab, then you can select it from the list;...
Page 196: Searching For A Registry Value
Your Installation on the Destination Computer To test the search, add a text box on one of the dialog boxes in the installation. In the text box’s Control Text field, enter the property name (surrounded by brackets) that you assigned to this search. (Example: [MY_PROPERTY].) This causes the value of the property to be displayed on the dialog box.
Page 197: Searching For A Previously-Installed Component
Your Installation on the Destination Computer Value Name Enter the name of the registry value. To find the default registry value, leave this blank. Search 64-bit portion of the registry (64-bit installations only.) Mark this to find registry keys that are designated as 64-bit components.
Page 198: Setting Version-Specific Windows Installer Options
Your Installation on the Destination Computer Read directory name from component keypath Select this operation if the component you are searching for contains only an empty directory (a Create Directory item) and has an empty key path. This operation returns a directory path. (Example: C:\Program Files\Application\.) If the keypath for this component is a file, ODBC item, or registry item, this operation fails.
Page 199 Your Installation on the Destination Computer Elevate Deferred Execution sequence only This is the preferred option for most installations. Typically, actions that require elevation should be in the Execute Deferred sequence. At run time, when the installation reaches the Deferred Execution sequence, the user is prompted for administrator credentials.
Page 200: About Uac Elevation Of Windows Installer Installations
Your Installation on the Destination Computer To set logging options for installations that will run under Windows Installer 4.0 or later, mark the appropriate check boxes: ! - Flush each line to the log a - Start up of actions Logs actions as they are started.
Page 201 Your Installation on the Destination Computer Options for elevating Windows Installer installations Option Description Elevate the Deferred In a typical MSI, only the Deferred Execution sequence should contain actions Execution sequence that write to a protected area on the destination computer. The installation runs in standard user mode until it enters the Execute Deferred sequence.
Page 202: About Uac Elevation Of An Entire Installation
Your Installation on the Destination Computer Option Description Create a standard user If an application is written to be installed and run by standard users without installation with no elevation elevation, you can bypass UAC elevation issues. The installation cannot contain actions that access a protected area on the destination computer.
Page 203: Setting Features For Installation Types
Your Installation on the Destination Computer installations. If you specified a name for the log file, only one log is created but it might appear to contain entries for two installations. This is normal. When the installation runs in maintenance mode, the installation is not elevated and a UAC prompt appears before the Execute Deferred sequence begins.
Page 204 Your Installation on the Destination Computer Description text This text appears next to the radio button on the Installation Type dialog box. To change the text for a specific installation type, select the installation type name in the upper-left list and change the text in the Description text box. Default features To set which features are turned on by default during installation, select an installation type name in the upper-left list and mark the check boxes of the...
Page 205 Your Installation on the Destination Computer Select Features dialog box Default features Windows Installer Editor Reference...
Page 206: Chapter 7: Organizing Your Installation Into Releases
Chapter 7 Organizing Your Installation Into Releases This chapter includes the following topics: About Releases on page 206 Customizing a Release on page 211 Setting Build Options for a Release on page 216 Adding Prerequisites to a Release on page 221 Creating a Clean Build on page 228 Creating Web-Based Installations With WebDeploy...
Page 207: Creating A New Release
Organizing Your Installation Into Releases x64 edition Itanium edition Creating Multiple, Platform-Specific Installations from One Project File on page 75. Working With the Releases Page Use the following buttons: Details Edit a release. Add a new release. Creating a New Release.
Page 208 Organizing Your Installation Into Releases To populate the file name or subdirectory with the value of one or more properties, enter one or more property names surrounded by brackets. Example: [ProductName].msi You can use one or more specific parts of a property’s value if its segments are period delimited.
Page 209: Associating A Release With Visual Studio Build Configurations
Organizing Your Installation Into Releases Target Platform Select the target platform for this release. This determines the Template Summary property of the compiled .MSI. The initial default is set by the Target Platform option on the New Installation File dialog box. If the installation previously contained only 32-bit releases, designating a feature or release as 64-bit enables the 64-bit areas of the Files and Registry pages as well as other 64-bit-related areas of the interface.
Page 210: Outputting A Multiple-Language Release
Organizing Your Installation Into Releases configuration, and the 64-bit release with the 64-bit configuration. Then, when you build the 64-bit configuration, only the 64-bit release is compiled. Platform configurations are not supported in Visual Studio 2003 or earlier. In those versions, you specify the build configuration only.
Page 211: Customizing A Release
Organizing Your Installation Into Releases Creating a Language Transform on page 290. During compile, the transforms are packaged inside the .EXE along with the .MSI. .EXE that launches external .MSI When you select this, you can use language transforms or you can create a separate .MSI for each language.
Page 212: Customizing Properties For A Release
Organizing Your Installation Into Releases The application doesn’t allow the end user to save files. The product’s name indicates it is an evaluation. The product’s summary informs the end user that this evaluation release doesn’t allow saving files. Note This page is enabled in a .WSI only. Customizing Properties for a Release Note This page is enabled in a .WSI only.
Page 213: Defining A Feature And Component Set For A Release
Organizing Your Installation Into Releases End users can see the summary information by right-clicking the compiled .MSI or .EXE in Windows Explorer and selecting Properties. Note In Windows Vista and later, the file Properties dialog box does not contain summary information.
Page 214: Sharing Settings Between Releases
Organizing Your Installation Into Releases To include a feature in this release, mark its check box. To exclude a feature, clear its check box. To select which components to include in this release: Click the feature name to display the feature’s components in the lower pane. Mark the check boxes of components to include.
Page 215: Example: Creating An Evaluation Release
Organizing Your Installation Into Releases Example: Creating an Evaluation Release This example describes how you could define an evaluation release for an application. In this example: The release is named Sample Evaluation. The application’s summary dialog box indicates that this is an evaluation release. Potential customers can use the evaluation version indefinitely, but they can’t save any files.
Page 216: Setting Build Options For A Release
Organizing Your Installation Into Releases Setting Build Options for a Release Note This page is fully enabled in a .WSI only. In an .MSI or .MST, you cannot add or delete. On the Build Options page, you can customize a release by selecting the format of output files and language options.
Page 217 Organizing Your Installation Into Releases an .MSI file that might or might not be embedded in the .EXE. This sets the Create a downloadable .EXE option on the WebDeploy page, and vice versa. WebDeploy .EXE and .INI Change the download information dynamically, perhaps as a result of end user input.
Page 218: About The Installation Of An .Msi Into An Svs Layer
Organizing Your Installation Into Releases Install normally if the SVS driver is not present Mark this option to install the .MSI normally if the SVS driver (Software Virtualization Agent) is not installed on the computer. If you clear this option and the SVS driver is not present, then the installation fails.
Page 219 Organizing Your Installation Into Releases WiseScript project file (.WSE) When you select the option on the Build Options page to install the .MSI into an SVS layer, a WiseScript project file (.WSE) is created, which when compiled creates the .EXE wrapper. You can edit this .WSE file from the Prerequisites page. Editing the WiseScript That Creates the Installation .EXE on page 227.
Page 220: About The Exclusion Of Files On The Build Options Page
Organizing Your Installation Into Releases Installs any other prerequisites that are specified on the Prerequisites page. These prerequisites are not installed into an SVS layer. Determines whether a compatible version of the SVS Driver (Software Virtualization Agent) is installed. If a compatible version of the SVS Driver is not found and if the SVS Driver runtime is not a prerequisite of the installation, one of the following happens: If you selected the option to install the .MSI normally on the Build Options page, the .EXE wrapper installs the .MSI normally and not into an SVS layer.
Page 221: About Maintenance Of An .Msi Installed Into An Svs Layer
Organizing Your Installation Into Releases The Build Options page contains options that let you use any of the following to exclude user data files from an SVS layer: Files extensions that are listed on the Files Association page. These extensions appear in the Extension table on the Tables tab.
Page 222: Adding A Windows Installer Or .Net Framework Runtime
Organizing Your Installation Into Releases Select the Windows Installer and .NET Framework runtimes to add. Specify whether to install the SVS Driver runtime. Add prerequisite files to run before the main installation. Prerequisite files are usually .EXE or .MSI files, but there is no restriction on their type. Add runtimes to run before the main installation.
Page 223: Adding The Svs Driver Runtime
Organizing Your Installation Into Releases To add a Windows Installer or .NET Framework runtime Select Installation Expert > Prerequisites page. From Current Release, select a release. Select the Windows Installer runtime version to pre-install. You can select a Windows Installer runtime for Windows 2000/XP/2003 and Windows Vista/2008.
Page 224: Adding A Prerequisite File
Organizing Your Installation Into Releases Note The options on the Prerequisites page are unavailable if Do not create an .EXE file is selected from .EXE Options on the Build Options page. SVS Driver runtime is unavailable if Install the .MSI into an SVS layer option is not selected on the Build Options page.
Page 225 Organizing Your Installation Into Releases From Current Release, select a release. To run the prerequisite files before checking the launch conditions of the .MSI installation, mark Don’t check the launch conditions of the .MSI installation until after running the prerequisites. By default, the .MSI launch conditions are checked after the installation of any runtimes that you select on the Prerequisites page and before any prerequisite files run.
Page 226: Adding A Runtime Prerequisite
Organizing Your Installation Into Releases If a prerequisite file or runtime requires a restart, you might need to edit the WiseScript to make the restart run smoothly. We recommend adding two Pause actions for 1000 milliseconds after a prerequisite or runtime that requires a restart. This works better than one Pause action for 2000 milliseconds.
Page 227: Editing The Wisescript That Creates The Installation .Exe
Organizing Your Installation Into Releases If a runtime-specific dialog box appears, complete it and click OK. Click OK on the Runtime Details dialog box. The runtime is added to the Prerequisites page. To edit or delete it, use the right- click menu.
Page 228: Creating A Clean Build
Organizing Your Installation Into Releases Click Edit Script at the right of the page. The Edit Script button is available only after you do one of the following: Add prerequisite files or runtimes on the Prerequisites page. Select Install the .MSI into an SVS layer on the Build Options page. Setting Build Options for a Release on page 216.
Page 229 Organizing Your Installation Into Releases Options for saving the clean build You set clean build options per release, which means you can have a different clean build location for each release. Check the clean build into a source code control system (SCCS). Every time you generate a clean build, any files in the installation that changed are checked into the SCCS.
Page 230: Creating Web-Based Installations With Webdeploy
Organizing Your Installation Into Releases The compiled files appear for each release whose Build check box is marked on the Releases page. Two log files are created; one shows compile actions and the other shows compile errors. To create a clean build in a directory Select Installation Expert >...
Page 231 Organizing Your Installation Into Releases runtimes, is downloaded whether or not it is needed on the destination computer. The resulting download can take a long time and tie up bandwidth. Note You cannot use WebDeploy to run patches (.MSP) or transforms (.MST). To distribute updates with WebDeploy, format the installation as an upgrade using the Upgrades page.
Page 232: The Webdeploy Process
Organizing Your Installation Into Releases See also: Tips for Creating an Efficient WebDeploy Installation on page 233 Creating a WebDeploy Installation on page 233 Uploading a WebDeploy Installation to the Web on page 235 The WebDeploy Process The following diagram shows how the WebDeploy™ process works when you distribute an .EXE with an embedded .MSI over the Internet.
Page 233: Tips For Creating An Efficient Webdeploy Installation
Organizing Your Installation Into Releases Tips for Creating an Efficient WebDeploy Installation Windows Installer version. For best results with WebDeploy, the destination computer should have Windows Installer 2.0 or later. For more efficient downloading, organize the installation into components. Only the components that are needed for the installation are downloaded.
Page 234 Organizing Your Installation Into Releases From .EXE Options, specify how the installation is created. This is linked to the .EXE Options field on the Build Options page. Create a downloadable .EXE Create an .EXE that is optimized for direct downloading from the Internet. The installation will compile to an .EXE that contains the download information, and an .MSI file that might or might not be embedded in the .EXE.
Page 235: Uploading A Webdeploy Installation To The Web
Organizing Your Installation Into Releases Note Be sure that the location you upload to does not violate the license agreement for the distribution of Microsoft runtime files. See also: Creating Web-Based Installations With WebDeploy on page 230 Uploading a WebDeploy Installation to the Web on page 235 Uploading a WebDeploy Installation to the Web Windows Installer version.
Page 236: Setting Up Media For Distribution
Organizing Your Installation Into Releases If the installation will pre-install any Windows Installer or .NET runtimes, use an FTP client to upload the following files: If you specified a 2000/XP Download URL on the WebDeploy page, upload the file InstMsi3.exe to that Web address. If you specified a .NET Runtime URL on the WebDeploy page, upload the .NET Framework file dotnetfx.exe to that Web address.
Page 237: Adding A Media Item
Organizing Your Installation Into Releases Copy the contents from the destination directories onto the media you will use for distribution. Note At least one media item is required. If the Media page contains only one item, you cannot delete it. Adding a Media Item Note This page is fully enabled in a .WSI only.
Page 238 Organizing Your Installation Into Releases If you select this option, you also might want to use short file names for uncompressed files outside the installation. See the description of Use short file names for files uncompressed outside of the install in Creating a New Release on page 207.
Page 239: Adding A Media Destination
Organizing Your Installation Into Releases Recommendations for common distribution media: Media Max Media Size Cluster Size CD-ROM 550 MB 2048 Bytes ZIP disk 100 MB or 250 MB 2048 Bytes Floppy disk 1440 KB 512 Bytes In the Media Destinations section, enter the directory where the installation is stored before you copy it to the distribution media.
Page 240: Including Features And Components In Media Items
Organizing Your Installation Into Releases Destination Directory Specify the holding directory in which the installation files are stored before they’re placed on the selected media. If you specify a maximum media size on the Media Details dialog box and do not specify destination directories, installation files are placed in folders with generic names (Disk1, Disk2, and so on) in the directory that contains the project file.
Page 241: Sharing Media Settings Between Releases
Organizing Your Installation Into Releases To include features and components in a media item Select Installation Expert > Media page. From Current Release, select a release. Double-click a media item. The Media Details dialog box appears. In the Include Features/Components section, click Add. The Include Items for Media dialog box appears.
Page 242: Example: Spanning An Installation Across Media And Sharing Media Size Information
Organizing Your Installation Into Releases Example: Spanning an Installation Across Media and Sharing Media Size Information You can span an installation across CDs and use the Share media destinations/size info with previous media entry option. Assume the following: The files for your application use 1.5 GB of uncompressed disk space. You want to distribute the application on two CDs.
Page 243 Organizing Your Installation Into Releases It is very important to change volume labels for your disks or CDs to match this value. Failing to do so will prevent the installation from working properly. Disk Name CD 1 Click OK. In the Media Destinations section, click Add again. The Media Destination Details dialog box appears.
Page 244: Chapter 8: Advanced Installations
Chapter 8 Advanced Installations This chapter includes the following topics: About the Mobile Devices Page on page 244 About Command Lines on page 251 Adding a Digital Signature to an Installation on page 262 Creating an Installation for Microsoft SMS on page 263 Creating a .NET Installation When You Have the .NET Framework on page 264...
Page 245: Process For Adding Mobile Device Support To An Installation
Advanced Installations application. It supports the Microsoft® Windows Mobile™ platform for Pocket PC and Smartphone devices. See About Mobile Device Package Editor in the Mobile Devices Package Editor Help. See also: Process for Adding Mobile Device Support to an Installation on page 245 About Windows Mobile Installations on page 245...
Page 246: Adding Windows Mobile Files
Advanced Installations 2002 platforms, but several of the application files are platform-dependent. When you create the installation, you assign the files to the device that supports that platform. When you compile, the Windows Mobile-specific files are placed in the Windows Mobile .CAB file, and the Pocket PC 2002-specific files are placed in the Pocket PC 2002 .CAB file.
Page 247 Advanced Installations To step through the wizard Complete the Application Information dialog box and click Next: Application Name Enter the name of the application you are installing. This appears in the list of applications on the Mobile Devices page. It also appears in the desktop computer’s mobile device software (the Add/Remove Programs dialog box, which is accessible from the Microsoft ActiveSync window).
Page 248: About Palm Os Installations
Advanced Installations Icon File To use a custom icon, enter the path to the .ICO, .EXE, or .DLL file that contains the icon. Icon Index Enter the resource number of the icon (in the .ICO, .EXE, or .DLL file specified above) to use from the icon file above.
Page 249: Adding Palm Os Files
Advanced Installations To install to the Palm user folder: When you create the Windows installer installation: Mark the Install File to Palm User Folder During Installation check box on the Palm File Details dialog box. Add the Installation Type and Palm User Information dialog boxes to the installation.
Page 250 Advanced Installations If the Mobile Devices page is not visible, select All or Palm Application from the Page Views drop-down list in Installation Expert. On the New Installation File dialog box, select the Palm Application template from the Predefined Templates category. Do this to add the mobile device installation to a new installation.
Page 251: About Command Lines
Advanced Installations See also: About the Mobile Devices Page on page 244 About Palm OS Installations on page 248 Process for Adding Mobile Device Support to an Installation on page 245 About Command Lines Command lines change the behavior of an .EXE for different work environments and user requirements.
Page 252 Advanced Installations To create a command line to apply to an installation Select Installation Expert > Command Line page. Click Add. The Command Line Details dialog box appears. Note Although you can enter a command line in the Command Line field, we recommend that you use the options provided in this utility for an optimal, error- free installation.
Page 253: Applying Ui Options To An Installation
Advanced Installations Repair Repair installed files. Applying a Repair Option to an Installation on page 257. Properties Change the value of public properties. Changing Public Properties in an Installation on page 257. Transforms Apply transforms to the installation package using the TRANSFORMS property. Applying Transforms to an Installation on page 258.
Page 254 Advanced Installations qr - Reduced UI Displays authored modeless dialog and built-in modal error-message boxes during the installation. qf - Full UI Displays both modal and modeless dialog boxes that have been authored into the internal user interface, and built-in modal error-message boxes during the installation.
Page 255: Applying Logging Options To An Installation
Advanced Installations Applying Logging Options to an Installation Not available in a transform. Command lines cannot be applied to a transform. You can use a command line to set logging options that determine what activities are logged during the installation. For information on logging options, see Logging in the Windows Installer SDK Help.
Page 256: Applying An Advertising Option To An Installation
Advanced Installations m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties e - All error messages To set logging options for Windows Installer 3.0 or later, mark log - log all information in the Windows Installer 3.0 or later section. This overrides any options you mark in the All Windows Installer versions section.
Page 257: Applying A Repair Option To An Installation
Advanced Installations Click OK. See also: Creating a Command Line To Apply to an Installation on page 251 Applying a Repair Option to an Installation Not available in a transform. Command lines cannot be applied to a transform. You can use a command line to set a repair option for an installation that determines the files that are reinstalled during a repair.
Page 258: Applying Transforms To An Installation
Advanced Installations For information on public properties, see Public Properties in the Windows Installer SDK Help. To change public properties in an installation Click the Properties tab on the Command Line Details dialog box. Creating a Command Line To Apply to an Installation on page 251.
Page 259: Applying Or Removing Patches With A Command Line
Advanced Installations Applying or Removing Patches With a Command Line Not available in a transform. Command lines cannot be applied to a transform. You can use a command line to update an installation by applying or removing patches. For information on patches, see PATCH Property and MSIPATCHREMOVE Property in the Windows Installer SDK Help.
Page 260 Advanced Installations “path\WFWI.EXE” “path\project file” /option You can also start Windows Installer Editor (WfWI.exe) in the Visual MSIDiff mode using the following command line: WFWI.EXE base_file compare_file Comparing Windows Installer Files on page 93. Do not confuse this list of command-line options with the command-line options that you can apply at run time to an .MSI through the executable msiexec.exe.
Page 261: Wfwi.exe Command Line Option Example
Advanced Installations Command-line options Description Compile silently If you don’t include this, error or informational messages might appear that require user intervention. (Not available in the Visual Studio integrated editor.) /l log_file_name Creates an additional compile log file in addition to compile.log, which is created automatically WFWI.EXE Command Line Option Example The following example shows how to compile an installation from the command line.
Page 262: Adding A Digital Signature To An Installation
Advanced Installations Adding a Digital Signature to an Installation Use the Digital Signature page to add an Authenticode digital signature to an installation file so its integrity and authenticity can be verified. Digital signature methods The file signing tool that is used to digitally sign a file depends on the type of your digital certificate: Public/private key pair files This method requires a credentials file (.SPC or .CER) and a private key file (.PVK).
Page 263: Creating An Installation For Microsoft Sms
Advanced Installations Certificate options Signtool.exe with Personal Information Exchange file Mark this to use signtool.exe and then specify the Personal Information Exchange file (.PFX) to use. This option requires a password. You will be prompted for the password during compile. Signcode.exe with public/private key pair files Mark this to use signcode.exe and then specify the credentials file (.SPC or .CER) that contains your Digital ID, and your private key file (.PVK).
Page 264: Creating A .Net Installation When You Have The .Net Framework
Advanced Installations Package Definition File To create a package definition file when the installation is compiled, mark one of the following check boxes. Verify that the installation’s name, version, and manufacturer are entered on the Product Details page, because that information is included in the package definition file.
Page 265: Creating A .Net Installation Without The .Net Framework
Advanced Installations About Microsoft .NET Technology on page 548 Requirements for Creating a .NET Installation on page 552 Frequently Asked Questions About Microsoft Windows Installer on page 546 Creating a .NET Installation Without the .NET Framework on page 265 Setting a Requirement on the System Requirements Page on page 187 (for information on setting the required .NET Framework version) Creating a .NET Installation Without the .NET...
Page 266: About Web Installations
Advanced Installations Use a computer that has the .NET Framework installed and has the assemblies. This typically is a development computer. For each .NET assembly, run the Assembly Registration tool (regasm) from the Visual Studio command prompt. Run regasm with the argument /regfile and specify a file name.
Page 267: Features That Support Web Installations
Advanced Installations Differences between the Files page and Web Files page Files page Web Files page You can create directories and add files You can create Web folders, virtual to them directories, and Web sites, and add files to them You can set NTFS-based (NT file system) You can set Web-based security on permissions on directories...
Page 268: Creating A Web Site
Advanced Installations SQL Connection dialog Let the end user select a SQL Server name and security credentials to generate a valid SQL Server connection string. The connection string can then be used elsewhere, such as in a Web.config file or on the SQL Server Scripts page.
Page 269 Advanced Installations Prior to Windows Vista, Microsoft Internet Information Server (IIS) supported the creation of new Web sites only on server operating systems, which excluded Windows 2000 Professional and Windows XP. For workstation operating systems that do not support the creation of a Web site, you can let end users create a virtual directory instead of a Web site.
Page 270: Creating A Virtual Directory
Advanced Installations box. This web.config file is required for the support of virtual directory creation in IIS 7.0 and later. 10. Click the Web Site UI tab. Use this tab to specify the installation options that will be available to the end user at run time. Setting Installation Options for a Web Installation on page 274.
Page 271 Advanced Installations A virtual directory is considered top-level if it is directly under Destination Computer, and is considered a child if it is under a Web site. To create a virtual directory Select Installation Expert > Web Files page. If you don’t see the Web Files page, select All from the Page Views drop-down list. From Current Feature, select a feature or condition.
Page 272 Advanced Installations The web.config file contains the settings that you select on the Details dialog box. This web.config file is required for the support of virtual directory creation in IIS 7.0 and later. 10. To specify the installation options that will be available to the end user at run time, do one of the following: If this is a top-level virtual directory, click the Web Site UI tab.
Page 273: Creating A New Web Folder
Advanced Installations To delete a virtual directory On the Web Files page, in the lower-left list box, select a virtual directory and click Delete. A message asks if you want to delete the corresponding physical directory and files. On the Files page or Visual Studio Solution page, you cannot delete a physical directory that is linked to a virtual directory.
Page 274: Setting Installation Options For A Web Installation
Advanced Installations Setting Installation Options for a Web Installation An important part of setting up a Web installation is specifying the installation options that will be available to the end user at run time. To do so, use the Web Site UI tab, which appears on the details dialog box for Web sites and top-level virtual directories.
Page 275: Setting Installation Options For A Child Virtual Directory
Advanced Installations Virtual Directory Mark this to let end users install Web resources to a virtual directory. If you select only this option, then this Web site will be installed as a virtual directory. Install as Virtual Directory on Workstation This applies only if the New Web Site option above is marked, and the installation is installed to an operating system whose IIS version does not support creation of a new Web site.
Page 276: About The Web Site Details Dialog
Advanced Installations The details dialog box appears. Click the Virtual Directory UI tab. To display installation dialog boxes to the end user at run time, mark Display Run- Time UI. This adds Web dialog boxes to the installation. When you mark this check box, the remaining options on the tab are enabled.
Page 277 Advanced Installations Tabs that do not appear in IIS Installation Settings Lets you override existing settings when installing over an existing Web site or virtual directory Creating a Web Site on page 268 or Creating a Virtual Directory on page 270. Web Site UI (Web sites and top-level virtual directories) Lets you specify the installation options that will be available to the end user...
Page 278: Installing Web Settings From A File
Advanced Installations See also: About Web Installations on page 266 Installing Web Settings From a File You can let the end user run your Web installation on multiple computers and set the same settings on each one without having to step through the Web dialog boxes. Example: An end user, who operates a Web farm, wants to run your installation with the same Web site settings on 12 computers.
Page 279: Configuring A Microsoft Sql Server During Installation
Advanced Installations Follow the guidelines at the beginning of the XML file. Only edit settings that are commented. On the destination computer, run the installation with the following command line: msiexec.exe /i "PathToMsi.msi" WISE_CONFIG_INPUT_PATH="PathToWebSettingsFile.xml" where PathToMsi.msi is the full path to the installation and PathToWebSettingsFile.xml is the full path to the edited XML file.
Page 280: Tips For Using The Sql Server Scripts Page
Advanced Installations Click the Replacement tab and specify text strings to be found and replaced within the SQL statements at install time. Specifying Replacements in SQL Statements on page 282. Click OK on the SQL Script Details dialog box. The script is added to the list on the SQL Server Scripts page. The SQL scripts are executed in the order they appear on the SQL Server Scripts page.
Page 281: Specifying Sql Statements
Advanced Installations Name A name for the SQL script is generated and displayed here. You can accept the default or enter a more descriptive name. If you later change this field, the script file is not renamed. A file with this name and the extension .SQL is added to the installation. Connection String Enter a connection string that connects to a specific Microsoft SQL Server and database.
Page 282: Specifying Replacements In Sql Statements
Advanced Installations Database Name Enter a name for the database to be created on the destination computer. Import Data Rows Mark this to populate the database’s tables with all its current data. This is unavailable until you mark the Import Tables check box below. Import Views Mark this to import the defined views of the database.
Page 283: Importing .Net Framework Security Settings
Advanced Installations Text to Find Enter regular text or formatted text, such as a bracketed property name. If you enter formatted text, it is resolved before the find and replace takes place. Example: If you enter [INSTALLDIR], the find and replace searches for the value of INSTALLDIR.
Page 284 Advanced Installations .NET Framework Security page Properties and values of the Code groups on code group last your computer. selected in the upper-left pane. Properties and Code groups you values of the have imported code group last from your selected in the computer into lower-left pane.
Page 285: Mts/Com+ Page
Advanced Installations MTS/COM+ Page Use the MTS/COM+ page to add MTS or COM+ application packages to an installation. The MTS/COM+ page is intended for software developers who know the computer names of the servers that contain MTS or COM+ server applications. Both MTS (Microsoft Transaction Server) and COM+ are steps in the evolution of the Component Object Model (COM) technology.
Page 286 Advanced Installations The MTS/COM+ Application Details dialog box appears. Complete the dialog box: Application Name Specify the MTS/COM+ application. You can only select from currently installed applications. GUID (Read-only.) This contains the GUID of the MTS/COM+ application that you select. Installation Type Select the installation type: Client...
Page 287: Chapter 9: Translating An Installation
Chapter 9 Translating an Installation This chapter includes the following topics: About the Languages Page on page 287 Defining and Translating Into Additional Languages on page 293 Translating Text Strings You Have Added or Changed on page 299 Resizing Dialog Controls After Translation on page 304 About the Language Menu on page 305...
Page 288 Translating an Installation Export text strings to a file that Do this when you define a new language, or you can send to a translator when you add or change any user interface elements in an installation. Exporting Selected Text Strings to a File page 300.
Page 289: Creating A Translated .Msi
Translating an Installation Note The Languages page is unavailable for transforms. Edit languages in the base .MSI. Creating a Translated .MSI You can translate an installation to another language and have it compile to one or more .MSI files. A separate .MSI is created for the default language plus each language that is marked on the Languages page.
Page 290: Creating A Language Transform
Translating an Installation installation file is named Sample, a file named Sample_German.msi is created during compile. If you specify an .MST file instead of an .MSI, this language is compiled to a language transform. Creating a Language Transform on page 290. Codepage, Language ID Leave the defaults in these fields.
Page 291: Sharing Language Settings Between Releases
Translating an Installation From Current Release, select a release. Mark the check box next to each language to create a language transform for. Some .MSI files might not have languages listed on the Languages page. In that case, you must use the .WSI that compiled the .MSI. Double-click the marked language.
Page 292: Removing A Language From An Installation
Translating an Installation settings of either of the linked releases is also applied to the other release, until you break the link. To break a link between releases Select Installation Expert > Languages page. From Current Release, select a release. Click Share at the right of the page.
Page 293: Defining And Translating Into Additional Languages
Translating an Installation To restore a language that was deleted If you use the Delete button on the Languages page to delete a language and its text strings from an installation, you can later restore that language to the installation if you have a file containing translated text strings for that language.
Page 294: About The New Language Wizard
Translating an Installation Warning If you export the strings to a text file, make sure that the first two fields in the text file are not translated. These are the table and key names for the text strings and must remain intact. Import the translated resource or text file.
Page 295: Defining A New Language And Exporting All Text For Translation
Translating an Installation If you select None, click Finish to add the language to the Languages page and exit the wizard. If you select Export or Import, click Next. Additional pages appear; for details, see the topics listed in the preceding step. Defining a New Language and Exporting All Text for Translation If the language you need is not one of the 25 pre-translated languages, you can define the new language on the Languages page, then export strings from the installation.
Page 296: Importing All Text Strings After Translation
Translating an Installation Click Next. The Export/Import Text Strings for Language page appears. If you have not had the strings translated, mark Export and click Next. The Export Default Strings page appears. Complete the page: Export As Select a file type for the text strings: Resource File Exports the strings to a Visual C++ style resource file;...
Page 297: Importing All Text Strings With The New Language Wizard
Translating an Installation To import all text strings using the Language Strings dialog box Select Installation Expert > Languages page. From Current Release, select a release. Click Strings at the right of the page. The Language Strings dialog box appears. From Language, select the language for which you will replace all text strings.
Page 298 Translating an Installation Click Add at the right of the page. The New Language wizard appears with the Specify Language Details page. Complete the page: Language Name Enter a name for the new language. Destination File (Optional.) Specify the full path for the translated installation file. You can create an .MSI or a transform (.MST).
Page 299: Translating Text Strings You Have Added Or Changed
Translating an Installation Translating Text Strings You Have Added or Changed When you add or change any user interface elements in an installation, you must translate those changes if you want them to appear in another language. Examples: error messages; disk prompts; text and controls on dialog boxes; descriptions or names for launch conditions, features, or shortcuts;...
Page 300: Exporting Selected Text Strings To A File
Translating an Installation the new dialog box displays in English, even in the Spanish version of the installation. You must export all the text on the new dialog box to a file, have it translated to Spanish, and then import the Spanish version of the text back into the installation. If you are translating the entire installation to a new language, you can export, translate, and import all text strings in the installation.
Page 301: Importing Selected Text Strings From A File
Translating an Installation New or changed strings in installation Export all strings that were added or changed in this installation. All strings in current language Export all the text strings in the language you selected from the Language drop-down list. All strings in default language Export the text strings in the default language for the .WSI.
Page 302: Translating Text Directly Without Exporting It
Translating an Installation The translated text strings are inserted into the installation. If you chose to compare the text strings during the import, an error message informs you when one or more text strings in the installation have been changed since the export.
Page 303: Changing Text In Installation Expert And Setup Editor
Translating an Installation If you need to translate larger amounts of text, export the text strings to a file. Translating Text Strings by Exporting to a File on page 299. To translate a small amount of text Select Installation Expert > Languages page. From Current Release, select a release.
Page 304: Resizing Dialog Controls After Translation
Translating an Installation Table Columns you can translate and edit ActionText Description, Template BBControl Text ComboBox Text Control Text, Help Dialog Title Directory DefaultDir DuplicateFile DestName Error Message Feature Title, Description File FileName LaunchCondition Description ListBox Text ListView Text Media DiskPrompt Property Value...
Page 305: About The Language Menu
Translating an Installation Conditions for controls on dialog boxes on page 438. Also see UserLanguageID Property in the Windows Installer SDK Help. About the Language Menu The Language menu lists all languages that have text translated in the installation. Use the Language menu to display translatable items in another language.
Page 306 Translating an Installation To create a template with a different default language in the Wise editor Select File menu > New. The New Installation File dialog box appears. In the Categories list, click Predefined Templates. In the Templates/Tools list, click the Windows Application icon. Mark Create .WSI or .WSM project file that can be compiled into an .MSI or .MSM and click OK.
Page 307 Translating an Installation To create a template with a different default language in the Visual Studio integrated editor Note This procedure describes how to create a template for an installation within a solution. You also can change the default language in templates that create a merge module within a solution, or a stand-alone installation or merge module.
Page 308: About The Default Release Language
Translating an Installation You can use this template to create installations in which the default language is the one you selected. About the Default Release Language The default release language is defined for a specific installation. It overrides the Default language on the Language menu during compile.
Page 309: Keeping Track Of Changed Text Strings
Translating an Installation See also: Exporting Selected Text Strings to a File on page 300 Importing All Text Strings After Translation on page 296 Importing Selected Text Strings From a File on page 301 Translating Text on the Language Strings Dialog on page 302 Keeping Track of Changed Text Strings Two columns in the Language Strings dialog box help you keep track of changed,...
Page 310: Language Ids
Translating an Installation Finnish French (Canadian) Greek Hindi Hungarian Indonesian Japanese Korean Norwegian Polish Portuguese (Brazil) Russian Romanian Spanish (Basque) Spanish (Catalan) Swedish Thai Turkish If the language you need is not listed here, you can send the installation text strings to a translator and then add the new language and the translated strings to the Languages page.
Page 311 Translating an Installation Language Sublanguage Language ID ANSI (decimal codepage notation) Dutch Dutch (Standard) 1043 1252 English American 1033 1252 English Australian 3081 1252 English British 2057 1252 English Canadian 4105 1252 English Ireland 6153 1252 English New Zealand 5129 1252 Finnish Finnish...
Page 312 Translating an Installation Language Sublanguage Language ID ANSI (decimal codepage notation) Turkish 1055 1254 Windows Installer Editor Reference...
Page 313: Chapter 10: Distributing An Installation
Chapter 10 Distributing an Installation This chapter includes the following topics: Package Distribution on page 313 WiseUpdate on page 319 Package Distribution When you complete and compile an installation, you can use Package Distribution to share or deploy it by: Copying an Installation to the Share Point Directory.
Page 314 Distributing an Installation To copy a package to the share point directory Select File menu > Distribute. The Welcome page appears. If you are in a .WSI that contains multiple releases, a drop-down list appears. Select a release. Mark Distribute to share point directory. Click Next.
Page 315: Copying An Installation To A Network Directory
Distributing an Installation If a package with resources and the same package path is already in the Software Manager database a warning message appears asking if you want to overwrite it. Click Yes to re-import the package. The installation or merge module is copied to the share point directory. From there, it can be imported into the Software Manager database through the Wise Package Studio Software Manager.
Page 316: Copying An Installation To An Ftp Server
Distributing an Installation See also: Package Distribution on page 313 Copying an Installation to an FTP Server Not available in the Visual Studio integrated editor. When you are ready to deploy an installation package to end users, you can use Package Distribution to copy the compiled installation to an FTP server.
Page 317: Performing An Administrative Installation
Distributing an Installation Note If this option does not work as you expect, open an FTP client, configure it with the same information you entered in Package Distribution, and make sure it works. (Windows contains a default FTP client.) See also: Package Distribution on page 313 Performing an Administrative Installation...
Page 318: Copying An Installation To Removable Media
Distributing an Installation Copying an Installation to Removable Media Not available in the Visual Studio integrated editor. When an installation is ready to deploy to end users, you can use Package Distribution to copy the compiled installation to floppy disks or other removable media, such as zip disks.
Page 319: Wiseupdate
Distributing an Installation The installation is copied to the media. You are prompted to insert new media as necessary. If you are distributing a single file that is too large for the media specified, you are prompted to insert a higher capacity media. If that is not possible, use the Media page to span the installation across multiple media.
Page 320: The Wiseupdate Process
Distributing an Installation The WiseUpdate Process Phase 1: Your Computer Your Web Server (FTP/HTTP): Contains the WiseUpdate When you first use WiseUpdate, you: update file that stores: 1. Develop the installation The current version number 2. Configure WiseUpdate and URLs to the installation files (FTP) specify: Contains the installation files...
Page 321: Using Wiseupdate In An Installation
Distributing an Installation Using WiseUpdate in an Installation To use WiseUpdate® effectively, you must use it in two or more successive versions of your application. Using it in one version of your application only enables that version to check for later versions over the Internet. Note To avoid web connection errors when you use WiseUpdate with IIS 6.0 or later, you must add a MIME type to the IIS server for each type of file that you let users download...
Page 322 Distributing an Installation This information tells the client when, how, and where to check the Web location for new versions. The first time you configure WiseUpdate, you enable that version to check for later versions over the Internet. To enable the Internet updating capability, you must use WiseUpdate for each successive version of your application.
Page 323: About The Wiseupdate Update File
Distributing an Installation If you place the WiseUpdate shortcut in the StartUp group on the destination computer, WiseUpdate Client runs when the destination computer is started or the end user logs on to Windows. If the check interval has been reached, WiseUpdate Client runs normally, prompting the end user to check for updates.
Page 324: Customizing The Wiseupdate Dialog Boxes
To customize the WiseUpdate dialog boxes In Windows Explorer, go to the following directory: Program Files\Symantec\Wise Installation Studio\Windows Installer Editor\WiseUpdt Right-click WiseUpdt.wse, select Properties, uncheck Read-only, and click OK. In WiseScript Editor or WiseScript Package Editor, open WiseUpdt.wse.
Page 325: Uploading Wiseupdate Files With An Ftp Client
Distributing an Installation Program Files\Symantec\Wise Installation Studio\Windows Installer Editor\WiseUpdt If the prompt about the Windows Installer SDK merge module naming convention appears, click No. In Installation Expert, on the Files page, delete WiseUpt.exe from the INSTALLDIR directory and add the one that you just edited.
Page 326: Options For Running Wiseupdate Client
Distributing an Installation WiseUpdate Client uses the HTTP connection information that you specified on the WiseUpdate page to read the WiseUpdate update file on the Web server. If you are running the same version of your application as that on the server, a message notifies you that you are running the latest version.
Page 327: Wiseupdate Tips
Distributing an Installation The installation adds a shortcut for WiseUpdate Client to the Startup group of the Windows Start menu on the destination computer. When the destination computer is started or the end user logs on to Windows, WiseUpdate Client silently checks the time elapsed since it last ran. If the number of days elapsed is greater than the check interval value, WiseUpdate Client prompts the end user to check for updates.
Page 328: Troubleshooting Wiseupdate
Distributing an Installation The .EXE of the .MSI/.EXE pair must be located somewhere on the Web and must be accessible to WiseUpdate users. It cannot be distributed through email or other mechanisms. On the WiseUpdate page, the connection information you enter must point to the location of the WiseUpdate update file on the Web server.
Page 329 Distributing an Installation the Web server and the FTP server might have different alias and user information, but point to the same directory. Updates for Windows Installer installations must be in the form of an upgrade or patch. If the end user has version 1.0.0 of your application installed, and you make some changes to it and upload it with a new version number, the WiseUpdate upgrade will fail unless you configured the updated package as an upgrade (using the Upgrades page) or a patch (using Patch Creation).
Page 330: Chapter 11: Upgrading Applications
Chapter 11 Upgrading Applications This chapter includes the following topics: About Upgrading Applications on page 330 Preparing for Software Updates on page 330 UpgradeSync on page 333 Patch Creation on page 335 Upgrades on page 345 About Upgrading Applications Windows Installer provides two main methods for upgrading installations: patching and upgrading.
Page 331: Determine The Form Of The Update
Upgrading Applications Planning for the next software update should start when you ship the first version of your application. To create an update, you must have access to previous versions of the installation. Always archive the shipping installation in a place that is accessible. Even if you compile and ship the installation as an .EXE, archive the .MSI, which is created alongside the .EXE.
Page 332: Determine The Product Code And Product Version
Upgrading Applications If the product code is changed, then the updated application can be installed alongside the original application, or can inadvertently be installed over the original application. Are not recommended for updating an application. Should only be used to update if one of the following is true: The update is so small that only the contents of a few files changed.
Page 333: Upgradesync
Upgrading Applications UpgradeSync Using UpgradeSync is one of the steps in preparing software for updates. Preparing for Software Updates on page 330. UpgradeSync compares the current package with the previous version of the package, and does the following to prepare the current package for a patch or upgrade: Changes the PackageCode, ProductCode, and ProductVersion properties if necessary.
Page 334 Upgrading Applications Complete the page: Small Update Select this to ship this installation as a patch or reinstall. Small updates generally contain minimal changes to the contents of files. This option changes the package code. Minor Upgrade Select this to ship this installation as a patch or reinstall. Minor upgrades generally contain changes such as new or removed features, files, or other items.
Page 335: Patch Creation
Upgrading Applications See also: Preparing for Software Updates on page 330 Patch Creation Use Patch Creation to create a Windows Installer patch file (.MSP) that updates installed versions of a Windows Installer-based application. A patch file can update one or several previous versions.
Page 336: About Patch Sequencing
Upgrading Applications See also: About Patch Sequencing on page 336 Creating a Patch File on page 337 For additional topics, see About Upgrading Applications on page 330. About Patch Sequencing Windows Installer 3.0 or later. Patch sequencing ensures that patches are applied in the correct order, regardless of the order in which they are actually provided to the destination computer.
Page 337: Creating A Patch File
Upgrading Applications Family 200: B, D See also: Specifying the Patch Sequence on page 343 Patch Creation on page 335 Sequencing Patches and MsiPatchSequence Table in the Windows Installer SDK Help Creating a Patch File Before you create a patch file, review the guidelines for patch creation. Patch Creation on page 335.
Page 338 Upgrading Applications Note The Microsoft Windows Installer engine is called to perform the administrative installation. If the operation fails for any reason, the error message generated by Windows Installer displays. To work around the error open the .MSI, set it to generate uncompressed files, and recompile.
Page 339 Upgrading Applications Patch Removal (Windows Installer 3.0 or later only.) To make this patch removable through Add/Remove Programs, click Allow Removal and complete the Patch Removal Settings page. Specifying Patch Removal Settings on page 345. Note Multi-patch Media Settings: During patch creation, entries are made in the Media table of the patch installation.
Page 340: Specifying Previous Versions For Patches
Upgrading Applications Specifying Previous Versions for Patches To specify a previous version for a patch Access the Previous Version Details page. Creating a Patch File on page 337. This page is not related to the System Search page in Installation Expert, which lets you search for files, registry entries, and components, or search .INI files.
Page 341: Advanced Upgrade Version Details
Upgrading Applications Advanced Upgrade Version Details To enter advanced upgrade version details Access the Advanced Upgrade Version Details dialog box. Creating a Patch File on page 337. Complete the dialog box and click OK: Patch GUID Each patch file is assigned a GUID, independent of product codes and upgrade codes.
Page 342 Upgrading Applications You can avoid this problem by signing patches that will be run under Windows Vista or later operating system. To do so: Make sure that the original installation was digitally signed. Add a digital signature to the patch, using the same certificate that was used to sign the original installation.
Page 343: Specifying The Patch Sequence
Upgrading Applications TimeStamp URL Specify the URL you use for your timestamping service. Timestamping lets end users distinguish between a certificate that has expired but was valid when it was used to sign the installation, and a certificate that was used to sign an installation while it was expired.
Page 344: Specifying Advanced Patch Settings
Upgrading Applications Sequence Within Family Enter a number to specify the order in which this patch should be applied, relative to other patches in this patch family. The default sequence number is the previous sequence plus 10. Product Code Typically, you should leave this field blank, which causes the patch to be applied to all targets in the family.
Page 345: Specifying Patch Removal Settings
Upgrading Applications Specifying Patch Removal Settings Windows Installer 3.0 or later only. You can make a patch removable through Add/Remove Programs. This lets end users uninstall a patch without having to uninstall the entire application. For information on which patches can be removed, see Uninstallable Patches in the Windows Installer SDK Help.
Page 346: Creating An Upgrade
Upgrading Applications What you need to create an upgrade The previous version or versions, which you are upgrading, must have been installed using Windows Installer. You need access to the .MSI of each version you are upgrading. If you do not have access to the .MSI files, you must have the upgrade code and version information from the .MSI files.
Page 347 Upgrading Applications Include maximum version in range Mark this to include the maximum version as a valid upgrade. If you clear this, only versions below the maximum version are upgraded. Languages This determines if an application should be upgraded based on its language. Enter a semicolon-delimited list of languages that should be upgraded by this installation.
Page 348: Chapter 12: Working With Source Paths
Chapter 12 Working With Source Paths This chapter includes the following topics: Using Source Control on page 348 About Path Variables on page 356 Source Paths in an Installation on page 359 About source paths You might find that you need to work with source paths during installation development. Project files (.WSI) reference files you add to the installation by their source path.
Page 349: Adding An Installation To Source Control
Working With Source Paths Enable the Source Control menu by marking the Enable source control check box in Wise Options. If you do not have an SCCS installed on your system, the Source Control menu is hidden and the Source Control tab in Wise Options displays an informational message.
Page 350 Working With Source Paths To add an installation to source control If the commands in the Source Control menu are unavailable, do the following: Select Tools menu > Options > Source Control tab. Mark Enable source control. This enables the Source Control menu. Click OK to exit Wise Options.
Page 351: Adding Files To An Installation In Source Control
Working With Source Paths Adding Files to an Installation in Source Control on page 351 Adding Files to an Installation in Source Control Not available in the Visual Studio integrated editor. When you add files to an installation, you must also add them to your source code control system (SCCS), even if you previously added the installation to source control.
Page 352: Checking Files Into Source Control
Working With Source Paths Checking Files Into Source Control Not available in the Visual Studio integrated editor. You can use this feature only if you’ve added the current installation to your source code control system (SCCS). If you check a file in, then try to work on it, you are prompted to save it with a new name because the file is locked for changes unless it is checked out first.
Page 353: Getting Latest Version Of Files
Working With Source Paths Using Source Control on page 348 Adding an Installation to Source Control on page 349 Getting Latest Version of Files Not available in the Visual Studio integrated editor. You can use this feature only if you’ve added the current installation to your source code control system (SCCS).
Page 354: Showing History Of The Installation File
Working With Source Paths The Undo Check Out dialog box appears, listing all files that have been checked out. Note When you add a installation to source control, the installation file (.WSI or .MSI) is added and is also checked out, so it might appear in this dialog box even if you previously did not check it out.
Page 355: Comparing The Current Installation To The Latest In Source Control
Working With Source Paths Note If you are using Microsoft Visual SourceSafe, the Difference Options dialog box appears. You might need to select the SourceSafe folder and the Windows folder to compare in the Compare and To fields. Then click the Project button for differences. To perform a compare using Visual MSIDiff instead, use the Compare to Latest menu command.
Page 356: About Path Variables
Working With Source Paths See also: Using Source Control on page 348 Adding an Installation to Source Control on page 349 About Path Variables Note (Visual Studio integrated editor only.) This feature is independent of the Configuration Manager feature in Visual Studio, which lets you store source files in Release and Debug directories.
Page 357: Turning Path Variable Substitution On And Off
Working With Source Paths Turning Path Variable Substitution On and Off The Path Variables page lets you define variables to replace commonly-used source paths. Once these variables are defined, you can turn them on and off. To turn path variable substitution on and off Select Installation Expert >...
Page 358: Creating A Path Variable Based On A Registry Value
Working With Source Paths To create a path variable based on an environment variable Select Installation Expert > Path Variables page. Click Add at the right of the page and select Environment Path Variable. The Environment Variable Path Variable Details dialog box appears. Complete the dialog box: Variable Name Enter any name, but do not use special characters or spaces.
Page 359: Source Paths In An Installation
Working With Source Paths Reg. Key Specify the complete key name of the registry value that contains a directory path. The registry browser that appears shows only key names (folder icons). You specify the value in Reg. Value below. Reg. Value Select the value to pull a directory name from.
Page 360: Changing Source Directories
Working With Source Paths To see a file’s path, go to the Files, Web Files, or Visual Studio Solution page and double- click a file in the lower-right list box. The File Details dialog box appears, which displays the path for the file in the Source Pathname field. If this field only displays a file name or is blank, then you are working in an .MSI that was compiled from a .WSI.
Page 361: Converting To Relative Source File Paths
Working With Source Paths All parts of the installation that reference these directories are updated. See also: Source Paths in an Installation on page 359 Converting to Relative Source File Paths You can convert the paths of source files to relative paths. You might do this to keep all your source files in a central version and source control system.
Page 362: Changing The Source Directory Dynamically During Compile
Working With Source Paths encountering errors. Instead of a path such as Y:\Application.ini, a file has a fully qualified path such as \\Server\Development\Application\Application.ini. To convert to UNC-based source file paths Select Tools menu > Convert Source Paths. In Visual Studio: Project menu > Convert Source Paths. The Convert Source Paths dialog box appears.
Page 363 Working With Source Paths Example: Enter SourceFiles in the Name field and enter C:\Development in the Value field. The directory path you enter here can be changed by command- line options during compile. To point source directories to the value of the property Select Tools menu >...
Page 364: Chapter 13: Merge Modules And Transforms
Chapter 13 Merge Modules and Transforms This chapter includes the following topics: About Merge Modules on page 364 Available Tabs and Pages in Merge Modules on page 365 Creating a Merge Module As a New Installation on page 369 Creating a Merge Module Within a Solution on page 371 Creating a Merge Module From Existing Components on page 373...
Page 365: Available Tabs And Pages In Merge Modules
Merge Modules and Transforms Merge modules that you create. Adding a Merge Module to an Installation on page 381. Predefined merge modules that install commonly-used software packages. You can download these from the Wise Web site or from other vendors’ Web sites. Downloading Redistributable Files on page 34.
Page 366: Setting Merge Module Details
Merge Modules and Transforms The panes on the Module tab show only the items you have added, unless you select to show empty folders and items from the right-click menu. The upper-right pane shows the contents of the item selected in the left pane. For an expanded view of a selected item, double-click the item in the right pane.
Page 367: Setting Dependencies For A Merge Module
Merge Modules and Transforms .NET Application A .NET merge module with only .NET elements. Mixed (.NET and Win32) A merge module that contains both Win32 and .NET elements. When this option is selected, the Generate COM interop registry keys for .NET Assembly check box on the Self-registration tab of the File Details dialog box is marked by default for all .NET assemblies you add to this merge module.
Page 368: Setting Exclusions For A Merge Module
Merge Modules and Transforms If you select multiple merge modules, they’re listed on the Dependencies page. Double-click a module name to open the Dependency Module Details dialog box for a specific merge module. Fields are populated with information extracted from the merge module. Complete the dialog box: Module ID To specify a different merge module, click Browse.
Page 369: Creating A Merge Module As A New Installation
Merge Modules and Transforms If you select one merge module, the Exclusion Module Details dialog box appears. If you select multiple merge modules, they’re listed on the Exclusions page. Double- click a module name to open the Exclusion Module Details dialog box for a specific merge module.
Page 370 Merge Modules and Transforms For information on file types, see File Types on page 68. The Target Platform section on the New Installation File dialog box appears only if Select platform in New Installation File dialog is selected in Wise Options. How to Specify the Target Platform on page 71.
Page 371: Creating A Merge Module Within A Solution
Merge Modules and Transforms Dependencies are other merge modules that must be included with this merge module, and exclusions are other merge modules that cannot be included with this merge module. Setting Dependencies for a Merge Module on page 367 and Setting Exclusions for a Merge Module on page 368.
Page 372 Merge Modules and Transforms Click OK. If you selected the Windows Application icon, a merge module project is created in the location you specified and is listed in Solution Explorer. Skip the next step. If you selected the Setup Wizard icon, the Wise Setup Wizard appears. Step through the Wise Setup Wizard: On the wizard’s Overview page, review the project settings.
Page 373: Creating A Merge Module From Existing Components
Merge Modules and Transforms See also: Available Tabs and Pages in Merge Modules on page 365 Creating a Merge Module From Existing Components You can create a merge module by moving components from a feature in an existing installation file or merge module into a new merge module. Note All the components you plan to move to the new merge module must be in the same feature.
Page 374: Creating A Configurable Merge Module
Merge Modules and Transforms The components you select are removed from this installation, compiled into the new merge module, and re-inserted in the form of a merge module. The new merge module is also available to other installations. See also: Setting Merge Module Details on page 366 Setting Dependencies for a Merge Module...
Page 375: Setting Configuration Item Details
Merge Modules and Transforms Click OK. The value you defined for the configurable item appears in the Value field, and the item appears in the Configuration Items list box. To add more values for the item, repeat the preceding two steps. If you add multiple values, multiple rows appear in the list box and the values are concatenated to create the entire substitution value.
Page 376 Merge Modules and Transforms RTF Text The installation author can enter any text in rich text format to replace the default value. Example: Use this when you allow a different license agreement to be selected. Text Drop-down List The installation author can select from a drop-down list to replace the default value.
Page 377: Specifying Drop-Down List Values For Substitution
Merge Modules and Transforms Non-nullable Mark this if a value is required for this configuration item. Default Value Enter the value that should appear on the Merge Module dialog box when the configurable merge module is added to an installation. This is the value that can be changed.
Page 378: Specifying A Key For Substitution
Merge Modules and Transforms merge module to an installation, the installation author selects from a list that shows the descriptive text. See Bitfield Format Types in the Windows Installer SDK Help. To specify a bitfield for substitution Access the Configuration Item Details dialog box from the Module Substitution dialog box.
Page 379: Example: Configuring An Item For A Merge Module
Merge Modules and Transforms To specify a key for substitution Access the Configuration Item Details dialog box from the Module Substitution dialog box. Creating a Configurable Merge Module on page 374. Complete the Configuration Item Details dialog box. Setting Configuration Item Details on page 375.
Page 380 Merge Modules and Transforms Display Name Enter “Short file name.” Description Enter “Choose whether to use a short or a long file name for this file.” Type Select Arbitrary Text. Default Value Enter “RELEAS~1.TXT.” Click OK. On the Module Substitution dialog box, your configuration item appears as short_name in the Configuration Items list box.
Page 381: About The Merge Modules Page
Merge Modules and Transforms See also: Creating a Configurable Merge Module on page 374 About the Merge Modules Page The Merge Modules page lets you add merge modules to an installation, edit settings for merge modules that you already added, and remove merge modules from an installation.
Page 382 Merge Modules and Transforms contains the merge module. The merge modules in this directory are added to the list of available merge modules. Setting Merge Module Directories on page 48. Click Download to add merge modules from the Wise Web site, other vendors’ Web sites.
Page 383: Editing Merge Module Details
Merge Modules and Transforms The merge modules are added to this installation. If any of the merge modules contain dependencies, Windows Installer Editor tries to add them by looking in the default merge module directory. Setting Dependencies for a Merge Module on page 367.
Page 384: About Transforms
Merge Modules and Transforms If the Value drop-down list appears, select a value. It will be either a bitfield value, a table, or text. If a text field appears its label indicates the type of data you can enter: Text Value Enter any text.
Page 385: Creating A Transform Based On An Existing .Msi
Merge Modules and Transforms installation for a particular department. Then during installation, you make sure that the appropriate transform is applied for each department. You can create the following types of transforms: A transform based on changes that you make to an existing installation. This lets you change any aspect of an installation.
Page 386: Setting Transform Details
Merge Modules and Transforms Note If you add files when editing a transform, a .CAB file is created along with the transform. When you apply the transform, make sure the .CAB file, the original .MSI, and the .MST are all in the same directory. Save the transform, using the .mst extension.
Page 387: Applying A Transform To An Installation
Merge Modules and Transforms Code page mismatch Suppress errors from occurring if the code page (language) setting of the transform does not match that of the base .MSI. Validation The following check boxes and fields let you require certain conditions to be true for the transform to be applied to the base .MSI.
Page 388: Multiple Instance Installations
Merge Modules and Transforms Creating a New Release on page 207. Select the Build Options page, select the new release from the Current Release drop-down list, and select .EXE that launches external .MSI from the .EXE Options drop-down list. Compile the installation, which creates an .EXE, an .MSI, and an .INI file. Open the .INI file, and add the following line: CmdLine=TRANSFORMS="TransformName.mst"...
Page 389 Merge Modules and Transforms Select Installation Expert > Instance Transforms page. In Instance Property, enter a property that will be replaced by a unique value in this instance of the installation. Product Name is pre-filled with the product name from the Product Details page. If you change it here, it is changed on the Product Details page.
Page 390: Installing Multiple Instances
Merge Modules and Transforms See also: Installing Multiple Instances on page 390 Installing Multiple Instances Note Multiple instance installations are supported only by the versions of Windows Installer released with Windows XP SP1 (2.0.2600.1106), Windows Server 2003 (2.0.3790.0), or later. Like other types of transforms, an instance transform must be applied to a base .MSI or patch during installation using a command-line option;...
Page 391: Chapter 14: Tools
Chapter 14 Tools This chapter includes the following topics: About Windows Installer Editor tools on page 391 ApplicationWatch on page 392 Convert SMS Installer or WiseScript Installation on page 393 Import Visual Studio Projects on page 395 Removing Dependencies from the Project Dependency Exclusion List on page 398 Manage Assembly Exclusions on page 399...
Page 392: Applicationwatch
Tools Manage Assembly Exclusions Move Components to Merge Module Creating a Merge Module From Existing Components on page 373. MSI to WSI Conversion Package Distribution Copy a compiled installation to an FTP server, to a local area network, or to removable media.
Page 393: Convert Sms Installer Or Wisescript Installation
Tools Use as many of the application’s features as possible to ensure that files used by rarely-used features are recorded. Do not use the application to print, because printing accesses Windows operating system and printer-specific files. Close the application, return to the Run Application dialog box, and click Finish. If a file that is part of a merge module is added, the Files in Merge Modules dialog box appears.
Page 394: Converting An Sms Installer Or Wisescript Installation
Tools To edit an .IPF file without converting it to a Windows Installer package, open it in WiseScript Editor or WiseScript Package Editor. The WiseScript tools natively support Microsoft SMS files. Converting an SMS Installer or WiseScript Installation When you convert an SMS or WiseScript installation, its contents are added to the Windows Installer installation that is currently open.
Page 395: Import Visual Studio Projects
Tools Pages in Installation Expert, such as the Files page, are populated based on the contents of the source installation. If you converted an .IPF, files are referenced from their original locations. If you converted an .EXE, files from the converted installation are stored in and referenced from the extract directory that you specified above.
Page 396: Importing An Installation From A Visual Studio Project
Tools Visual Basic projects in the Visual Studio integrated editor The Import Visual Basic tool lets you import a Visual Basic 5 or 6 project file into an installation file. You specify information about the project, and the tool extracts information, such as source file paths, and integrates it into a new or existing installation.
Page 397 Tools Specify the directory on your computer where Visual Basic 5 or 6 is installed. This directory contains the support files that must be included in the installation because they are needed by the Visual Basic program. Go to To complete the import in either editor on page 397.
Page 398: Removing Dependencies From The Project Dependency Exclusion List
Tools Select a file and click Browse to locate missing files. Click Next. The Installation Files page appears. The Installation Files page lists the files that were detected during the scan and will be added to the installation. To add or remove files in the installation, click Add or Delete and then click Next. The Application Installation Information page appears.
Page 399: Manage Assembly Exclusions
Tools Assembly dependencies that are in the exclusion list are never added to the installation, even if the .NET assembly is rescanned, or if you add a new assembly that has the same dependency. Use the Manage Assembly Exclusions tool to remove dependencies from the exclusion list so that they can appear in future assembly scans.
Page 400: Converting An .Msi To A .Wsi File
Tools Converting an .MSI to a .WSI File By default, MSI to WSI Conversion extracts files and merge modules from an .MSI to a directory you select. It then creates a project file (.WSI) that references those files and merge modules. The project file, in turn, can be edited in Windows Installer Editor, and then compiled to a new .MSI file.
Page 401: Specifying Merge Module Source Directories
Tools Click Finish. If any source files or associated .CAB files are not in the location specified in the .MSI, they are listed on the Files Not Found page and source paths are not created for those files. You must find them and add them to the new .WSI. The new .WSI is created at the location you specified, the current .MSI is closed, and the new .WSI is opened.
Page 402: Specifying File Source Directories
Tools On the Select Directory dialog box, select the directory that contains replacement merge modules for all the merge modules you have selected and click OK. Merge modules are matched by GUID, a unique identifier attached to Windows Installer files, rather than by name. If the search is unsuccessful, a dialog box lists the merge modules that were not found.
Page 403 Tools The Select Directory dialog box appears. Select a directory and click OK. The selected files will be extracted to this directory instead of the default source directory. Complete the MSI to WSI Conversion wizard. To replace one file with a file on your computer On the File Sources page, select a file to replace.
Page 404: Package Validation
Tools Conversion cannot change the paths to point to your local computer, because your local computer only contains one copy of the file. For these files, either leave them set to the default, which will extract all copies of the file from the .MSI, or individually replace them with the appropriate files from your computer.
Page 405 Tools To validate a package Open the installation file (.MSI or .WSI), merge module (.MSM or .WSM), or transform (.MST) to test. Select Tools menu > Package Validation. (In Visual Studio: Project menu > Package Validation.) The Welcome page appears. To view the description of a validation module, select the module in the list.
Page 406: Customizing Validation Modules
Tools If the issue was found by a Microsoft validation module, see ICE Reference or Merge Module ICE Reference in the Windows Installer SDK Help for details. If the Correct button is enabled when you select an issue, click it to correct the issue.
Page 407: Predefined Validation Modules
Tools Note When customizing a predefined validation module, customize a copy of the .CUB file to retain the original file. To customize validation modules Start Package Validation and click Customize on the Welcome page. Validating a Package on page 404. The Customized Validation Rules dialog box appears.
Page 408 Tools Component design Checks that the proper files have been placed into each component and that the same file has not been placed into multiple components. Uninstall support Checks that the package does not reference non-Windows Installer uninstall utilities. Files in shared folders Checks that no executable files have been placed in shared directories.
Page 409: Windows Vista/Windows 7 Validation
Windows Vista or later operating system and specify the full path to WiseVistaIce.cub. Example: "C:\Program Files\Symantec\Wise Installation Studio\bin\getwrpitems.exe" "C:\Program Files\Symantec\Wise Installation Studio\Windows Installer Editor\Validation\wisevistaice.cub" The GetWRPItems.exe utility deletes the contents of both tables and rebuilds them based on the WRP information on your computer.
Page 410: Wise Task Manager
Tools The Welcome page appears. Click Next. The installation is searched and the Results page appears. Select the files to remove from the installation and click Next. The Removing Files page appears. If you ran this tool from the Tools menu, the Compile This Installation check box appears when the removal process finishes.
Page 411: Using Wise Task Manager
Tools When a user runs one of the managed operations listed above, Wise Task Manager queues them and executes them in the order in which they are received. An operation is performed after any other operations that are in the queue for that computer. Use Wise Task Manager to: Cancel the tasks of managed operations.
Page 412 Tools To view a task’s details, select the task and click Details. To change the tasks that appear, click Options on the Wise Task Manager dialog box. By default, Wise Task Manager displays only the tasks belonging to operations you run that do not have a status of Completed.
Page 413: Chapter 15: Setup Editor
Chapter 15 Setup Editor This chapter includes the following topics: About Setup Editor on page 413 Product Tab on page 415 Features Tab on page 417 Components Tab on page 423 Tables Tab on page 430 About Setup Editor Setup Editor provides an in-depth view of all changes that you make to an installation. You can make those changes in Setup Editor or Installation Expert.
Page 414 Setup Editor Setup Editor window in Windows Installer Editor The upper-right pane displays contents of the item selected in The left pane lists the left pane. items for the selected Double-click tab. Expand folders items to edit to see their contents them.
Page 415: Product Tab
Setup Editor Components Add, edit, and delete individual components of the installation. Each component is one action the installation performs. Example: installing a file, changing the registry, and so on. Components Tab on page 423. Module This tab appears only when you are in a merge module file. Add, edit, and delete the components, files, registry entries, and other installation modifications contained in the merge module.
Page 416: Specifying Summary Information
Setup Editor Specifying Summary Information Use the Summary icon in Setup Editor to set the value of a summary item. End users can see the summary information by right-clicking the compiled .MSI or .EXE in Windows Explorer and selecting Properties. Note In Windows Vista and later, the file Properties dialog box does not contain summary information.
Page 417: Features Tab
Setup Editor Features Tab The Features tab lets you manipulate an installation’s features and all corresponding items. It displays a tree structure that lists all components, merge modules, files, registry entries, and other installation items associated with each feature. Working With Components and Features on page 547.
Page 418: Assigning A Component To A Feature
Setup Editor Folder Creating a Folder in Setup Editor on page 421 Duplicate file entry Creating Duplicate File Entries on page 421 Environment variable Adding an Environment Variable on page 176. File association Advertising Icon on page 420. Adding File Associations on page 176.
Page 419: Modules Icon
Setup Editor To assign a component to a feature In Setup Editor > Features tab, right-click a feature and select New > Component Assignment. The Assign Components to Feature dialog box appears. The dialog box lists all components in the installation, except those already assigned to the currently selected feature.
Page 420: Advertising Icon
Setup Editor Click the Modules icon. The merge modules in the selected feature appear in the upper-right pane. If the Advertising icon does not appear, right-click and select Hide Empty Folders/ Items. See also: About Merge Modules on page 364 Features Tab on page 417 Advertising Icon...
Page 421: Creating A Folder In Setup Editor
Setup Editor Creating a Folder in Setup Editor The Create Folder icon in Setup Editor lets you add a new empty directory under an existing directory. You also can create directories on the Files, Web Files, or Visual Studio Solution pages in Installation Expert, where you can also use wildcards to add files to directories automatically.
Page 422: How To Ensure The Installation Of A Duplicate File
Setup Editor Specify the following: Existing File Specify the path for the file to be duplicated. Dest. Directory Specify the directory on the destination computer in which the duplicate file should be installed. To add a subdirectory to the directory you selected, click New Folder and enter a folder name.
Page 423: Components Tab
Setup Editor Components Tab The Components tab lets you manipulate an installation’s components. It displays a tree structure that lists all files, registry entries, and other installation items contained in each component. It also indicates any component errors. Installation Expert automatically creates the appropriate components for each item you add and organizes them according to a component rule set you select.
Page 424: Component Errors
Setup Editor Environment variable Adding an Environment Variable on page 176. File association Advertising Icon on page 420. Adding File Associations on page 176. File Adding Files to an Installation on page 130. INI file Creating and Editing .INI Files on page 171.
Page 425: Adding And Editing A Component
Setup Editor A shortcut is assigned to the component, but the key path for the shortcut is not a file. Registry keys are created in HKEY_CURRENT_USER, but the key path is not for a registry key in HKEY_CURRENT_USER. See also: Components Tab on page 423 Adding and Editing a Component...
Page 426 Setup Editor For some conditions, you might need to add a special merge module that addresses a limitation of Windows Installer. Using Conditions With Features on page 119. When you add a 64-bit component to the installation, the 64-bit component check box below is marked automatically and the condition (VersionNT64) is added to this field.
Page 427 Setup Editor Never overwrite if key path exists Mark this to prevent the component from being installed if the item specified as the key path already exists. 64-bit component When this is marked, it designates the component as 64-bit. The target directory and the component must both be either 32-bit or 64-bit.
Page 428: Moving Items Between Components
Setup Editor Extract advertising information from registry file Mark this to take information from the .REG file and places it into the advertising tables instead of the registry tables if possible. Click OK on the Component Details dialog box. If the installation has only one feature, the component is added to that feature. If the installation has more than one feature, the Select Feature(s) to Assign Component to dialog box appears.
Page 429: About The Key Path
Setup Editor About the Key Path To determine whether a specific component is installed, Windows Installer looks for the component’s key path rather than looking for every item in the component. If it finds the item that is specified as the key path, it assumes that all other items that make up the corresponding component, and therefore, the component, are installed.
Page 430: Adding Published Components
Setup Editor See also: Components Tab on page 423 Adding Published Components Published components let applications written specifically for Windows Installer refer to one or more components by a single identifier. Example: Do this to add the same published component to each component in a feature. At run time, the installation only needs to check for one published component to determine if the feature is installed.
Page 431 Setup Editor Reasons to edit tables directly To use the few features, such as ReserveCost, that are not available anywhere but on the Tables tab. To add a table to store data that is non-Windows Installer standard. Example: If you create a custom action that stores data, you must create a new table in which to store it.
Page 432: Creating A New Table
Setup Editor of the primary key column with an added underscore character. Example: An external key to the File column of the File table is always named File_. An optional, second heading row shows the field’s data type, string length if applicable, and whether the field can be null.
Page 433: Creating A New Row In A Table
Setup Editor Primary Key Mark this to indicate that this field is a primary key in this table. A table can have more than one primary field. Localizable Mark this to indicate that this field should be translatable. If you distribute this installation in another language, the data in this field will be translated.
Page 434: Editing Existing Tables
Setup Editor Editing Existing Tables On the Tables tab, you can directly edit any data in the Windows Installer database. You also can delete rows from tables and delete tables. Warning Deleting, adding, or editing table data directly is not recommended unless you are an experienced Windows Installer developer with a clear understanding of Windows Installer database technology.
Page 435: Finding Validation Errors
Setup Editor Assigning a Component to a Feature on page 418 Finding Validation Errors On the Tables tab, you can search for tables that contain errors and you can search for individual validation errors. These are quick ways to search for validation errors while you are working on a package.
Page 436: Editing Binary Data In The Icon Table
Setup Editor Editing Binary Data in the Icon Table On the Tables tab, you can edit binary data in the Icon table. Most items in this table are graphics (example: shortcut icons). You can export binary files for editing and then import them back into the installation.
Page 437: Chapter 16: Using Conditions And Properties
Chapter 16 Using Conditions and Properties This chapter includes the following topics: Conditions on page 437 Properties on page 445 Conditions Conditions are like expressions: they evaluate to a true or false value. You associate conditions with different elements of an installation such as features, components, actions, dialog boxes, and dialog box controls to determine whether something happens or not.
Page 438 Using Conditions and Properties condition or feature. These changes can include adding files, registry entries, services, and ODBC. Items that you add to a feature are installed on the destination computer only if the feature is installed. Items that you add to a condition are installed only if the feature is installed and the condition is true.
Page 439: Condition Guidelines
Using Conditions and Properties Conditions attached to control events You can attach an event to a control. The event can have an associated condition. You might attach events to Next buttons that specify what event happens if the Next button is clicked. Example: Click the Installation Type dialog in Setup Editor >...
Page 440: Examples Of Conditions
Using Conditions and Properties When adding conditions to the Launch Conditions icon, you can add conditions that check properties or environment variables, but you cannot add conditions that check the installed state of a component or feature. You might need to include the merge module CondFix.msm, that fixes certain Windows Installer limitations related to component conditions.
Page 441: Creating Conditions With Condition Builder
Using Conditions and Properties Add CondFix.msm to an installation if you add a component condition that checks the installed state of a component or feature. The Windows Installer Editor installation places CondFix.msm in the default merge modules directory, or you can download it with the Download Redistributables wizard. This merge module appears on the Select Merge Module dialog box when you add a merge module on the Merge Modules page.
Page 442: Checking The Value Of A Property
Using Conditions and Properties Use the () buttons to enclose parts of the condition, which changes the order of precedence. Use the " button to enclose literal text. Lists Fields Select the kind of item the condition checks. You can check the installed state for features and components, and you can check the value of properties and environment variables.
Page 443: Checking The Value Of An Environment Variable
Using Conditions and Properties Creating Conditions With Condition Builder on page 441. In the Fields list, click the Property folder. The Values list displays a list of properties and directories that are initialized by this installation. More properties appear than in other lists of properties, such as the Properties icon in Setup Editor >...
Page 444: Checking If And How A Feature Or Component Is Currently Installed
Using Conditions and Properties Checking If and How a Feature or Component is Currently Installed A feature or component might be installed to run locally, from the source, or advertised, which are all options you can set when installing a component or feature. Note You cannot add this type of condition to the Launch Conditions icon in Setup Editor >...
Page 445: Properties
Using Conditions and Properties To check if and how a feature or component will be installed by this installation Open the Condition Builder. Creating Conditions With Condition Builder on page 441. In the Fields list, click the Feature or Component folder. In the Values list, click the name of the feature or component.
Page 446: How Do You Use Properties
Using Conditions and Properties Created by you in the You can create properties in the Properties icon in Setup installation database Editor > Product tab. Also, some dialog boxes that contain a property drop-down list also contain a New button with which you can create a new property.
Page 447: Creating A New Property
Using Conditions and Properties In conditions You can use properties inside conditions. You do not need to enclose the property name in brackets. Conditions determine whether something happens or not. As formatted text on dialog boxes To display the value of a property or write the value of a property to a file, you must enclose the property name in square brackets.
Page 448 Using Conditions and Properties Note You cannot enter other properties to set the value of a new property because text you enter is interpreted literally. This is not true for some specific Windows Installer properties, such as DiskPrompt and PrimaryFolder. To set a property to the value or values of other properties, use the Set Property custom action.
Page 449: Chapter 17: Working With Dialogs
Chapter 17 Working With Dialogs This chapter includes the following topics: About Dialogs on page 449 Using the Dialogs Page on page 452 Using the Dialogs Tab on page 456 Editing Dialog Details on page 458 Creating a New Dialog on page 460 About Dialog Controls on page 461...
Page 450: About The Wizard Dialogs
Working With Dialogs The Dialogs tab shows all dialog boxes that are part of an .MSI. Any of these dialog boxes can appear in different situations: Install Dialogs The Install Dialogs appear during a normal installation, if no command-line options are used to run an advertisement, administrative, or silent installation.
Page 451 Working With Dialogs Readme dialog Importing Text into License and Readme Dialogs page 455. User Information dialog Lets end users enter their name, company, and product ID, and indicate whether the software should be installed for all users or only for the current user. The Product ID field does not appear to the end user if the ProductID property (select Product tab >...
Page 452: Using The Dialogs Page
Working With Dialogs Logon Information dialog In Wise Installation Studio, this appears in installations that are started from the Server Application template in the New Installation File dialog box. You can add it to any installation by using the New Dialog Wizard. Adding the Logon Information Dialog on page 476.
Page 453: Changing The Theme Of Dialogs
Working With Dialogs Warning If this installation contains Web resources, then the list of dialog boxes might include Web (IIS) dialog boxes. Only enable or disable the Web dialog boxes as a group. Enabling individual Web dialog boxes can prevent the installation from working properly. To view a dialog box Click the dialog box name in the Dialogs list.
Page 454: Adding And Editing Dialog Themes
Working With Dialogs Warning Changing themes might delete dialog box customizations in installations that were created in previous versions of this Wise product. To preserve dialog box customizations, leave None selected in Default Theme. To change the dialog box theme Select Installation Expert >...
Page 455: Importing Text Into License And Readme Dialogs
Working With Dialogs When you create a new theme, the images you specify are copied to a new subdirectory in the Themes directory. The location of the Themes subdirectory varies. Installation Resources and Their Locations on page 32. Theme images you create must be in .BMP format. To quickly create theme images, copy and edit a set of predefined images.
Page 456: Changing The Order Of Web Dialogs
Working With Dialogs Note If you encounter error messages or formatting problems when you import the file, open it in Wordpad, save it as .RTF, and re-import it. Some computers cannot import files with formats other than .RTF. Also, only the standard .RTF settings are supported for the License and Readme dialog boxes.
Page 457 Working With Dialogs Warning Do not edit the Web (IIS) dialog boxes, except to change their order (as a group) in the installation sequence. Editing the Web dialog boxes might cause unexpected, undesirable behavior, including damage to the installation. Also, any operation within this product that affects the installation’s user interface will regenerate the Web dialog boxes, therefore, any changes you make to them will be lost.
Page 458: Adding Controls To Dialogs
Working With Dialogs See User Interface Levels in the Windows Installer SDK Help. In Setup Editor > Dialogs tab, clear the check box next to Welcome Dialog Wizard. Adding Controls to Dialogs Add controls to dialog boxes on the Dialogs tab in Setup Editor. Because of limitations with Windows Installer, do not place dialog box controls on top of graphics.
Page 459 Working With Dialogs Setup Editor > Dialogs tab: Right-click the name of a dialog box in the left pane, and select Details. Installation Expert > Dialogs page: Select the dialog box and click the Details button. The Dialog Details dialog box appears. Warning If you are using the Installation Types page to manage the Installation Types dialog box, do not change any details on the Installation Type dialog box.
Page 460: Creating A New Dialog
Working With Dialogs Use Custom Palette Mark this to use a custom color palette on displays with 256 colors or less. This usually makes the dialog box look better, provided only one dialog box is on the screen at a time. Note If you get details for the Custom Property dialog box, an Edit button appears on the Dialog Details dialog box.
Page 461: About Dialog Controls
Working With Dialogs Specify where in the sequence the new dialog box should appear. If Move Up and Move Down buttons appear, use them to move the new dialog box within the list. If they do not appear, then you must select a dialog box in both the After and Before columns.
Page 462 Working With Dialogs Combobox A combination edit field and drop-down list control that lets the end user select a predefined value or enter a value Directory Combobox Displays a combination directory list and path edit field to let the end user specify a directory Directory Listbox Displays the folders below the main part of the current path This is intended to be used with the path edit control.
Page 463: Editing Dialog Controls
Working With Dialogs Editing Dialog Controls Warning Do not edit the Web (IIS) dialog boxes, except to change their order (as a group) in the installation sequence. Editing the Web dialog boxes might cause unexpected, undesirable behavior, including damage to the installation. Also, any operation within this product that affects the installation’s user interface will regenerate the Web dialog boxes, therefore, any changes you make to them will be lost.
Page 464 Working With Dialogs Note If you encounter error messages or formatting problems when you import the file, open it in Wordpad, save it as .RTF, and re-import it. Some computers cannot import files with formats other than .RTF. Max Characters (This replaces the Control Text field for an edit field control.) Enter the maximum number of characters the end user can enter.
Page 465 Working With Dialogs uses the property RADIO but has the Indirect check box marked. The property FIRST, SECOND, or THIRD is set to the check box state based on the setting of the radio button. Scrollbar on left side On a scrolling field control, places the scrollbar on the left instead of the right. (Usually used with the Right-To-Left Reading check box below.) Integer Restricts end users to entering only integers in this control.
Page 466: Setting An Event On A Control
Working With Dialogs Password Makes an edit control display asterisks instead of the characters that the end user types. This is typical of controls that require entry of a password. Bitmap Replaces the control’s text with a bitmap. The control’s text is used as a key to the Binary table to point to the bitmap data.
Page 467: Assigning Help To A Control
Working With Dialogs Control Events for details on each control event. Argument Enter the argument for the event. If no value is passed for that argument, the event is ignored. See Control Events in the Windows Installer SDK Help; click an event name to see valid arguments.
Page 468: Setting The Graphic For A Control
Working With Dialogs To add a new condition, click Add. To edit a selected condition, click Details. To remove a selected condition from this control, click Delete. When you click Add or Details, the Control Condition Details dialog box appears, where you set the following options: Action The action to take when the condition is true.
Page 469: Organizing And Aligning Controls On Dialogs
Working With Dialogs When you click Add or Details, a details dialog box appears, where you can specify the text that appears in the control. The settings available on this tab vary depending on the type of control. Text The text of the button or list item. Value The value returned to the control’s property when the item is selected.
Page 470: Aligning Dialog Controls
Working With Dialogs Overlapping graphics and controls When dialog box 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.
Page 471: Centering Dialog Controls
Working With Dialogs In Visual Studio: Format menu > Align > Lefts/Rights/Tops/Bottoms All selected controls are aligned with the master control. Centering Dialog Controls You can center controls on a dialog box in relation to the dialog box boundaries. To center dialog box controls In Setup Editor >...
Page 472: Setting Dialog Tab Order
Working With Dialogs Horizontal Spacing > Make Equal. Space items left to right. Vertical Spacing > Make Equal. Space items up and down. All selected controls are spaced evenly on the dialog box. Setting Dialog Tab Order You can determine the tab order of controls on dialog boxes. To prevent unexpected control layering, set the dialog box’s tab order to include any graphic or control that is overlapped by another control.
Page 473: Adding Billboards To A Dialog
Working With Dialogs The billboard control The billboard control is associated with a feature and an installation action. It also defines how many bitmaps, icons or text controls are displayed, and in what order. You create one billboard control for each bitmap, icon, or text control.
Page 474 Working With Dialogs Click the small outline and resize and move it to accommodate the content items you plan to add. You can adjust it later. Note Although a default billboard area is already created, you also can create your own. Right-click the dialog box and select Add >...
Page 475: Obtaining Logon Information From A Dialog
Working With Dialogs Repeat this step to add as many controls as you have content items. The controls you create do not appear on the dialog box. You can only see their content items, which you add in the next step. Add content items to each billboard control: Right-click the dialog box and select Billboards >...
Page 476: Adding The Logon Information Dialog
Working With Dialogs Let the end user create a new NT user account during installation, if the end user has the privileges to do so. Let the end user specify an existing NT user account during installation. Populate the properties MYUSERNAME and MYPASSWORD with the logon information specified by the user.
Page 477: About The Sql Connection Dialog
Working With Dialogs Step through the wizard to create a new dialog box. Creating a New Dialog on page 460. Edit the dialog box text as needed to communicate the purpose of the user account to the end user who installs your application. Guidelines for using the Logon Information dialog box Make sure you customize the text on the Logon Information dialog box to communicate the logon information’s purpose to the end user.
Page 478: Adding The Sql Connection Dialog To An Installation
Working With Dialogs Adding Prerequisites to a Release on page 221. The Browse button appears on the SQL Connection dialog box only if SQL Client Tools (osql.exe) is installed on the destination computer. When the end user clicks the Browse button, a drop-down list appears with the SQL Servers on their network. If the Browse button does not appear, the end user must enter the SQL Server name.
Page 479: Editing Additional Sql Connection Dialogs
Working With Dialogs Step through the wizard to create a new dialog box. Creating a New Dialog on page 460. Edit the dialog box text as needed to communicate its purpose to the end user who installs your application. See also: About the SQL Connection Dialog on page 477 Editing Additional SQL Connection Dialogs...
Page 480: Adding The Custom Property Dialog
Working With Dialogs Setting SQL Connection Strings on page 280. Example: Use the WISE_SQL_CONN_STR1 property for the connection string. See also: About the SQL Connection Dialog on page 477 Adding the Custom Property Dialog The Custom Property dialog box lets you specify Windows Installer properties that can be set by the end user during installation.
Page 481 Working With Dialogs to set the property. This is limited to about 275 characters, because of the size of the field that appears on the Custom Property dialog box. Display property value as asterisks during installation To mask the property value during installation, select the property name in End User-Configurable Properties and mark this check box.
Page 482: Chapter 18: Macro Editor
Chapter 18 Macro Editor This chapter includes the following topics: About the Macro Editor on page 482 About Macro Files on page 482 About the Macro Editor Window on page 485 About the Macro Editor The Macro Editor provides access to Wise Automation, which programmatically controls Windows Installer Editor.
Page 483: Creating, Editing, And Running A Macro
Macro Editor The Macro Editor doesn’t let you save a .WBS file under a different name. To rename a macro file, change the file name in Windows Explorer. See also: Creating, Editing, and Running a Macro on page 483 About the Macro Editor Window on page 485 Creating, Editing, and Running a Macro The Macro Editor is similar to the Microsoft Visual Basic Editor.
Page 484: Events That Can Trigger A Macro
Macro Editor (Visual Studio integrated editor only.) In MSI Script, right-click in the Installation Sequence pane and select Macros. The Macro dialog box appears. From Macro Is Run, select: Manually to edit a manually-run macro. On Windows Installer Editor event to edit a macro that runs on an event. In the list box, select the macro to edit.
Page 485: About The Macro Editor Window
Macro Editor Event What you could do with a macro AddFile Have each .DLL or .EXE file you add marked Read-only or have all .DLL files placed into the System directory. Have a specific set of files added each time you start a new installation.
Page 486 Macro Editor Members Is context-sensitive and gives you properties and methods in the context of a clicked object If your pointer is not on an object when you select this item from the right-click menu, then it lists all available properties and methods. Properties and methods for an object are all predefined in Windows Installer Editor.
Page 487: Chapter 19: Debugger For Windows Installer
Chapter 19 Debugger for Windows Installer This chapter includes the following topics: About the Debugger on page 487 Running the Debugger on page 488 About the Debugger The Debugger for Windows Installer is an easy-to-use tool that lets you step through an installation to isolate and resolve problems.
Page 488: Running The Debugger
Debugger for Windows Installer Table List Lists all the tables in the installation in a window named _Tables. To open a table, double-click its row in the Table List. Move from one open table to another by clicking the corresponding tab at the bottom of this window. You can edit temporary table fields only.
Page 489: Setting Properties And Applying Transforms In The Debugger
Debugger for Windows Installer The installation is saved and compiled if you made changes since the last compile. You are prompted to select an .MSI if you defined more than one release. The debugger window opens. Set breakpoints if desired. Setting and Clearing Debugger Breakpoints.
Page 490: Evaluating Conditions
Debugger for Windows Installer then run the installation, it pauses at the breakpoint and waits for another command. You can set multiple breakpoints. To set a breakpoint Click the action at which you want to set a breakpoint, then press F9. You can set breakpoints on sequences and control events only.
Page 491: Chapter 20: Using Msi Script
Chapter 20 Using MSI Script This chapter includes the following topics: About MSI Script on page 491 The MSI Script Window on page 492 Editing Sequences on page 496 Calling WiseScripts with Custom Actions on page 498 Guidelines for Using Custom Actions on page 504 Launching a Custom Action from a Dialog on page 509...
Page 492: The Msi Script Window
Using MSI Script The MSI Script Window To access MSI Script™, click the MSI Script tab at the bottom of the main application window. Installation Mode Restricted Areas Actions Sequences Installation Mode Installation modes represent the different ways an installation can be run. Choose whether to work on a normal installation, an advertisement installation, or an administrative installation.
Page 493 Using MSI Script Installer installation you create, but each mode is run only under certain circumstances. Installation modes are not used with merge modules. For information on dialog box groupings, see About Dialogs on page 449. Normal Installation Select this installation mode to edit the sequences that are run during a normal installation.
Page 494: Adding A Custom Action Outside A Sequence
Using MSI Script Add a custom action outside a sequence Adding a Custom Action Outside a Sequence. Add a custom action to multiple sequences Adding a Custom Action to Multiple Sequences on page 494. Quickly review and edit custom actions If your custom actions are scattered, you can quickly review and edit them without scanning through each sequence to find them.
Page 495: About Installation Sequences
Using MSI Script Using the Custom Action Location Tab on page 539. From Sequence, select a sequence. In the list box of actions, select an action and click Add. The action is added to the sequence, below the action you selected. If you are in a merge module, the layout of the Location tab is different.
Page 496: Editing Sequences
Using MSI Script In the Visual Studio integrated editor, you cannot select an installation mode, because the standard Visual Studio Find dialog box is used. Note You cannot replace text using this feature, but you can replace text in Setup Editor > Tables tab.
Page 497: About The Standard And Custom Tabs
Using MSI Script If Statements - Conditions (blue) Use If Statements to indicate that a condition is attached to the actions between the If Statement and its corresponding End statement. Remarks (green) Remark statements document the script. Remarks that explain how the script works are already added to new scripts you create.
Page 498: Commenting Out Script Lines
Using MSI Script You can also copy and paste actions to other locations in the installation sequence. However, each time you copy and paste an action, an entirely new copy of the action is stored in the installation. To avoid this duplication, see Adding a Custom Action to Multiple Sequences on page 494.
Page 499: Examples Of Wisescripts You Run From An .Msi
Using MSI Script Calling a WiseScript .EXE versus calling a regular .EXE Creating a custom action that calls a WiseScript .EXE is similar to calling a regular .EXE, except that communication can take place between Windows Installer and WiseScript. This is possible through the use of the Get Windows Installer Property, Set Windows Installer Property, and Evaluate Windows Installer Condition actions in the WiseScript.
Page 500: Using A Wisescript To Install A License File
Using MSI Script In MSI Script, add a custom action to Run a WiseScript from Installation and specify the WiseScript you wrote. When an end user runs the Windows Installer installation, it calls the WiseScript, which parses the path. When the Windows Installer installation continues running, APPLICATION_PATH contains Application.exe.
Page 501: Uninstalling Changes Made By A Wisescript
Using MSI Script The sample WiseScript looks like this (the script lines are numbered for clarity): 1. Get Windows Installer Property SERIALNUM into SERIALNUMBER 2. Get Windows Installer Property INSTALLDIR into MAINDIR 3. Set Variable EDITION to LEFT$(SERIALNUMBER,1) 4. Check free disk space 5.
Page 502 Using MSI Script Add a Run WiseScript From Installation custom action and set the following: Custom Action Name: ActionInstallCorePlus WiseScript .EXE File: C:\Plus\CorePlus.EXE Command Line: Leave this blank. On the Properties tab, leave the defaults. Add an End Statement. The above script lines install CorePlus, which in this example is A.dll. In the following script lines, you make provisions for the uninstall.
Page 503: Troubleshooting: When Wisescript Custom Actions Fail On Windows Vista Or Later
Using MSI Script This causes the WiseScript to create a log in the installation directory. Add an Install File(s) script action and set the following: Source Pathname: path to Unwise32.exe Unwise32.exe is in the WiseScript Editor subdirectory of this product’s installation directory.
Page 504: Guidelines For Using Custom Actions
Using MSI Script Open the installation in Windows Installer Editor. Windows Installer Editor checks for custom actions that run a WiseScript. Each WiseScript .EXE is updated in memory with a manifest specifying the asInvoker run level. A task appears in the Task List to record each change. If the WiseScript .EXE had an associated row on the Windows Installer Editor Resources page, the Refresh check box for that resource is cleared so that the .EXE on disk is not used during the next compile.
Page 505: Guidelines For Custom Action Location
Using MSI Script Guidelines for Custom Action Location General Place the custom action as high in the sequence as possible where it executes properly. If it doesn’t execute properly when you test it, keep moving it lower in the sequence until it works. If the custom action uses information that’s gathered during the User Interface sequence, place it after the actions that gather the information you need.
Page 506: Guidelines For Custom Action Conditions
Using MSI Script Restricted Areas in the Sequence If an action has restrictions on its placement in the sequence, the restricted areas are shaded in the Installation Sequence list when you select the action in the Actions list. Place the action in a non-restricted area. Restrictions are defined by Windows Installer functionality.
Page 507: Guidelines For Calling Vbscripts And Jscripts
Using MSI Script Limitations Nested installations are supported according to the Windows Installer specification. While nested installations may sometimes be necessary, we do not recommend using them because of the restrictions on their use. See a list of restrictions at the end of Nested Installation Actions in the Windows Installer SDK help.
Page 508: Guidelines For Calling .Dlls
Using MSI Script From Embedded Code. They let you store the script inside the custom action and resolve formatted property names and other references. Make sure the destination computer contains the runtime for JScript or VBScript. You can call scripts using custom actions, but you must author the JScript or VBScript. The built-in Macro Editor is not meant to author JScripts and VBScripts that you call from custom actions.
Page 509: Launching A Custom Action From A Dialog
Using MSI Script In the User Interface or Execute Immediate sequences, you can send Windows Installer properties to the .DLL function as parameters. The property’s current value is passed to the function, and, if the function changes that value, the new value is put into the corresponding property.
Page 510: Troubleshooting Custom Actions
Using MSI Script On the Events tab, in the Publish Events group box, click Add and complete the dialog box: Event Select DoAction. Argument Enter the name of the custom action. The name is case-sensitive. When the installation is run, the button you added appears on a dialog box. When the end user clicks the button, the custom action you specified is run.
Page 511: Chapter 21: Custom Action Reference
Chapter 21 Custom Action Reference This chapter includes the following topics: About Custom Actions on page 512 Call Custom DLL From Destination on page 512 Call Custom DLL From Installation on page 513 Call Custom DLL From Installed Files on page 514 Call DLL From Installation on page 516 Call Custom DLL From Installed Files...
Page 512: About Custom Actions
Custom Action Reference Run WiseScript From Destination on page 534 Run WiseScript From Installation on page 535 Run WiseScript From Installed Files on page 536 Set Directory on page 537 Set Feature State on page 538 Set Property on page 538 Terminate Installation on page 539 Using the Custom Action Location Tab...
Page 513: Call Custom Dll From Installation
Custom Action Reference Usage Double-click the custom action and complete the Details tab: DLL File Specify a .DLL file that exists on the destination computer to call during installation. Type the path to the .DLL as it will be on the destination computer, but use a Windows Installer directory property (enclosed in brackets) to specify the beginning of the path.
Page 514: Call Custom Dll From Installed Files
Custom Action Reference to call ABC32.dll, one to call ABCx64.dll, and one to call ABCItanium.dll. Place each custom action inside a condition block that checks for the appropriate platform. Manage the .DLL on the Resources page, which reflects the Binary table. Note Before being passed to Windows Installer, calls you make with Call Custom DLL actions are passed through a .DLL that facilitates the passing of parameters.
Page 515: Configuring .Dll Parameter Settings
Custom Action Reference appropriate platform. Example: Your .WSI contains a 32-bit release, an x64 release, and an Itanium release. You add three Call Custom .DLL actions to the project: one to call ABC32.dll, one to call ABCx64.dll, and one to call ABCItanium.dll. Place each custom action inside a condition block that checks for the appropriate platform.
Page 516: Call Dll From Installation
Custom Action Reference In the Execute Immediate or User Interface sequences only, you can send Windows Installer properties to the .DLL function as parameters. The property’s current value is passed to the function and, if the function changes that value, the property is updated back in the installation.
Page 517: Call Dll From Installed Files
Custom Action Reference You cannot send a variable parameter list to the .DLL. You can send only the handle to the installation, which means the .DLL must be written specifically for Windows Installer. To avoid these restrictions, use a “Call Custom DLL...” action instead. Usage Double-click the custom action and complete the Details tab: Custom Action Name...
Page 518: Call Jscript From Embedded Code
Custom Action Reference Function Name Type the name of the function within the .DLL file to call. See also: Guidelines for Calling .DLLs on page 508 Guidelines for Custom Action Location on page 505 Using the Custom Action Properties Tab on page 542 Using the Custom Action Location Tab on page 539...
Page 519: Call Jscript From Installed Files
Custom Action Reference Tips Manage the file on the Resources page, which reflects the Binary table. Use the script to read and write properties to the installation. The destination computer must contain the script’s runtime. Usage Double-click the custom action and complete the Details tab: Custom Action Name Enter a unique name that begins with a letter or underscore.
Page 520: Call Jscript From Property
Custom Action Reference See Standard Actions Reference in the Windows Installer SDK Help. Script File Specify a script file to call during installation. It must have already been added to this installation on the Files page. Script Function Call (Optional.) Type the name of the function within the script to call. Run Script in Win64 Process (64-bit installations only.) Mark this if the script needs to access 64-bit functionality and run in a 64-bit process.
Page 521: Call Vbscript From Embedded Code
Custom Action Reference Guidelines for Custom Action Location on page 505 Using the Custom Action Properties Tab on page 542 Using the Custom Action Location Tab on page 539 Custom Action Type 53 in the Windows Installer SDK Help Call VBScript From Embedded Code This custom action runs VBScript code that is embedded inside this custom action.
Page 522: Call Vbscript From Installed Files
Custom Action Reference Usage Double-click the custom action and complete the Details tab: Custom Action Name Enter a unique name that begins with a letter or underscore. It can contain numbers and periods. It must not match the name of any Windows Installer standard action. See Standard Actions Reference in the Windows Installer SDK Help.
Page 523: Call Vbscript From Property
Custom Action Reference See also: Guidelines for Calling VBScripts and JScripts on page 507 Guidelines for Custom Action Location on page 505 Using the Custom Action Properties Tab on page 542 Using the Custom Action Location Tab on page 539 Custom Action Type 22 in the Windows Installer SDK Help Call VBScript From Property This custom action runs VBScript code that is stored inside a Windows Installer property.
Page 524: Download File From Internet
Custom Action Reference Tips If this custom action is within a condition, the message is displayed only when the specified condition is met. Example: You could display a message if end users marked a check box on a dialog box. You would associate the check box with a property and then set up a condition to check if the property was true.
Page 525: End Statement
Custom Action Reference Usage Double-click the custom action and complete the dialog box: Source URL Enter the URL of the file to download, including the name of the file. Example: http://www.site.com/readme.pdf. Destination Directory Specify the file path, including file name, on the destination computer where the file should be downloaded.
Page 526: Execute Program From Installation
Custom Action Reference See Standard Actions Reference in the Windows Installer SDK Help. Working Directory Using a non-bracketed Windows Installer directory property (Example: INSTALLDIR), specify the working directory of the .EXE file to call. When the .EXE file is run on the destination computer, its current working directory is set to the directory you specify here.
Page 527: Execute Program From Installed Files
Custom Action Reference Custom Action Type 2 in the Windows Installer SDK Help Execute Program From Installed Files This custom action calls an .EXE file that is installed by this installation. Tips Before you add this custom action, add the file to be called to the Files page in Installation Expert.
Page 528: If Statement
Custom Action Reference Property Specify a property that will store the path and name of the .EXE. Select a property or type a new property name. Command Line (Optional) Enter command-line options to pass to the .EXE file. See also: Guidelines for Custom Action Location on page 505 Using the Custom Action Properties Tab...
Page 529: Install Msi From Installation
Custom Action Reference For best results, place this custom action in the Execute Immediate sequence after the InstallFinalize action. Usage Double-click the custom action and complete the Details tab: Custom Action Name Enter a unique name that begins with a letter or underscore. It can contain numbers and periods.
Page 530: Install Msi From Relative Path
Custom Action Reference On the Properties tab, In-Script Options is unavailable for this custom action and Processing only allows synchronous execution. For best results, place this custom action in the Execute Immediate sequence after the InstallFinalize action. Usage Double-click the custom action and complete the Details tab: Custom Action Name Enter a unique name that begins with a letter or underscore.
Page 531: Launch Web Page
Custom Action Reference Tips This custom action is not available in an Administrative Installation. The installation being called must be a Windows Installer installation. On the Properties tab, In-Script Options is unavailable for this custom action and Processing only allows synchronous execution. For best results, place this custom action in the Execute Immediate sequence after the InstallFinalize action.
Page 532: Open Document From Installed Files
Custom Action Reference In Web Page URL on the Launch Web Page dialog box, designate the URL to open during installation. The URL must be complete. Example: http://www.symantec.com. See also: Download File From Internet on page 524 Post Data to HTTP Server...
Page 533 Custom Action Reference Tips You must have an ASP or CGI program set up to accept data from HTTP POST operations. The computer running the installation must have a valid Internet connection (such as dial-up networking). If you place this action in the User Interface or Execute Immediate sequences, you can use formatted text strings, such as [PROPERTY], in the Destination URL and Text to Post fields.
Page 534: Remark
Custom Action Reference Launch Web Page on page 531 Guidelines for Custom Action Conditions on page 506 Remark The Remark action lets you put comments in sequences to document what is happening in the script. In Remark, type the comment. To place a blank line in the sequence, add a Remark action, but leave Remark blank.
Page 535: Run Wisescript From Installation
Custom Action Reference Guidelines for Custom Action Location on page 505 Using the Custom Action Properties Tab on page 542 Using the Custom Action Location Tab on page 539 Troubleshooting: When WiseScript Custom Actions Fail on Windows Vista or later page 503 Run WiseScript From Installation This custom action stores a WiseScript .EXE in the Binary table of this installation file...
Page 536: Run Wisescript From Installed Files
Custom Action Reference See also: Examples of WiseScripts You Run From an .MSI on page 499 Calling WiseScripts with Custom Actions on page 498 Guidelines for Custom Action Location on page 505 Using the Custom Action Properties Tab on page 542 Using the Custom Action Location Tab on page 539 Troubleshooting: When WiseScript Custom Actions Fail on Windows Vista or later...
Page 537: Set Directory
Custom Action Reference unavailable if the WiseScript .EXE File field is empty or if a corresponding .WSE file does not exist for the specified .EXE file. Command Line (Optional) Enter the command-line options to send to the .EXE. Example: Enter /s to make the WiseScript run silently.
Page 538: Set Feature State
Custom Action Reference Using the Custom Action Location Tab on page 539 Custom Action Type 35 in the Windows Installer SDK Help Set Feature State This custom action sets the installation state of a feature at run time. The installation state determines how or whether a feature is installed.
Page 539: Terminate Installation
Custom Action Reference brackets. For information on formatted text strings, see Formatted in the Windows Installer SDK Help. See also: Guidelines for Custom Action Location on page 505 Using the Custom Action Properties Tab on page 542 Using the Custom Action Location Tab on page 539 Custom Action Type 51 in the Windows Installer SDK Help Terminate Installation...
Page 540: Using The Custom Action Location Tab For Merge Modules
Custom Action Reference Note The Location tab is an alternate way to perform tasks that you normally perform in the User Interface, Execute Immediate, or Execute Deferred sequences. You can move and copy custom actions by using editing functions in these sequences. The main use for this tab is to click the No Sequence option, which causes this action to not run unless an event invokes it.
Page 541 Custom Action Reference Note When you add a custom action to a merge module, you’ll notice that the Custom Action Name field automatically contains the GUID of the merge module. You should leave the GUID as part of the custom action name to ensure adherence to Windows Installer guidelines for naming custom actions in merge modules.
Page 542: Using The Custom Action Properties Tab
Custom Action Reference Using the Custom Action Properties Tab The Properties tab appears on the details dialog box for most custom actions. However, sometimes options are unavailable or display different choices based on what kind of custom action you added and where you added it. In this dialog box, you set options that determine when and how the custom action is run.
Page 543 Custom Action Reference run asynchronously. See Rollback Custom Actions in the Windows Installer SDK Help. Commit only Select this if the action should be executed later, during installation of the commit script, which is invoked upon successful completion of the installation script. Commit actions run in deferred execution mode.
Page 544: Using The Custom Action Description Tab
Custom Action Reference does not check the exit code. This option is not supported for Install MSI custom actions. This option is not supported for Install MSI custom actions or if you selected Rollback Only in the In-Script Options list above. Scheduling Options If you add the custom action to both the UI Sequence and the Execute Sequence, but you want to limit the number of times it actually runs, select an option here.
Page 545: Chapter 22: Windows Installer And .Net Technologies
Chapter 22 Windows Installer and .NET Technologies This chapter includes the following topics: About Microsoft Windows Installer on page 545 About Microsoft .NET Technology on page 548 About Microsoft Windows Installer Wise products integrate closely with Microsoft Windows technologies. The installations you create are in Microsoft Windows Installer format and are run on the destination computer by the Windows Installer engine.
Page 546: Frequently Asked Questions About Microsoft Windows Installer
Windows Installer and .NET Technologies Frequently Asked Questions About Microsoft Windows Installer How is Windows Installer different from Windows Installer Editor? Microsoft Windows Installer is a Microsoft technology for writing, managing, and installing applications. The Microsoft Windows Installer service, which resides permanently on the destination computer as part of the operating system, includes a Windows Installer executable named msiexec.exe.
Page 547: Working With Components And Features
Windows Installer and .NET Technologies How does Windows Installer Editor support advertisement? In Windows Installer Editor, you can set default advertisement on a per-feature basis on the Feature Details dialog box. If you advertise features, however, you must include Windows Installer function calls within the application to perform a feature-level installation of the necessary files when an advertised entry point is invoked.
Page 548: About Guids
Windows Installer and .NET Technologies For information on how Windows Installer handles components and features, see the following topics in the Windows Installer SDK Help: Windows Installer Components Component Management Components and Features Organizing Applications into Components See also: About Microsoft Windows Installer on page 545 About GUIDs GUID stands for globally unique identifier.
Page 549: Frequently Asked Questions About Microsoft .Net
Windows Installer and .NET Technologies Windows Installer Editor simplifies the process of creating installations for .NET applications, automating the process by extracting most of the installation details from your assemblies. Windows Installer 2.0 or later only The ability to create .NET installations is supported only by Windows Installer 2.0 or later.
Page 550 Windows Installer and .NET Technologies called as though they were COM components. At run time, the common language runtime marshals data between COM objects and managed objects as needed. Search for “Interoperating with Unmanaged Code” in the MSDN Library (msdn.microsoft.com/library/). What is an assembly? An assembly is the primary building block of a .NET application.
Page 551 Windows Installer and .NET Technologies private directory for the exclusive use of the application. A version of the assembly is also globally registered on the system and made available for any application that binds to it. The global version of the assembly can be the version installed with the application or an earlier version.
Page 552: Requirements For Creating A .Net Installation
Windows Installer and .NET Technologies Requirements for Creating a .NET Installation The ability to create .NET installations is supported only by Windows Installer 2.0 or later. When you create a .NET installation, you should have the .NET Framework installed on your computer. If the .NET Framework is installed on your organization’s development computers, but not on the computer used to build installations, it is possible to create a .NET installation.
Page 553: Appendix A Wise Custom Actions
Appendix A Wise Custom Actions Windows Installer Editor uses custom actions to add functionality that is not available with the Windows Installer standard actions. When you use certain features, such as custom actions that call a .DLL, Wise custom actions are added to the installation. Warning Removing Wise custom actions might cause problems with the installation.
Page 554 Wise Custom Actions Custom action Description DiagnosticAppSearch Enumerates the entries in the AppSearch table and evaluates the expressions using the MSIEvaluate Property function. It then retrieves the value of the property and reports the results. DiagnosticCheckDiskSpace Evaluates the disk costing and identifies computers that don’t meet the requirements.
Page 555 Wise Custom Actions Custom action Description DiagnosticFileAssociationConflict Processes the Extension table and checks the registry for support for each extension. This test opens the registry key for the extension. If the key exists, then the extension is already registered. The existing value of the key is compared with the ProgId to be registered;...
Page 556 Wise Custom Actions Custom action Description SetPatchMode Sets the REINSTALL property to the list of features in the previous version of the user’s application and sets the ADDLOCAL property to the list of features, if any, that were added to the installation in the new version of the application.
Page 557 Wise Custom Actions Custom action Description WiseGetIISFeaturesEnabled Sets properties (CGIENABLED, ISPAIENABLED, ASPENABLED, ASPDOTNETENABLED, SSIENABLED, IDCENABLED, FPEXTENABLED, and WebDAVENABLED) to show which features are enabled in IIS. This is useful for setting launch conditions to ensure that the destination computer has the required environment for the installation.
Page 558 Wise Custom Actions Custom action Description WiseUpgradeCheck When you add upgrade information to the Upgrades page, this action is added to work around issues where the Windows Installer runtime does not detect previous versions of the application. WiseUpgradeCheckEx When you add upgrade information to the Upgrades page, this action is added to work around issues where the Windows Installer runtime does not detect previous versions of the application.
Page 559: Appendix B Wise Tables
Appendix B Wise Tables Wise tables contain information that is related to items you added in Windows Installer Editor. Most of these tables do not appear in the compiled .MSI, unless noted otherwise or unless you use an .MSI file as the project file. Some of the tables listed below are available in certain Wise products only.
Page 560 Wise Tables Wise table Remains in Description .MSI? WiseFirewallSetup Stores options that are configured on the Firewall Exceptions page WiseInstanceTransforms Contains information about instance transforms that are defined in Installation Expert > Instance Transforms page. WiseLangString Contains all strings for all languages currently defined in the installation.
Page 561 Wise Tables Wise table Remains in Description .MSI? WisePocketPCRegistry Contains information about each Pocket PC registry key and all of its attributes WisePocketPCShortcut Contains information about each Pocket PC shortcut and all of its attributes WisePrerequisites Contains information on prerequisites that are added to the installation on the Prerequisites page WiseRelease Contains a list of all releases in the installation...
Page 562 Wise Tables Wise table Remains in Description .MSI? WiseVSDropFile (Visual Studio integrated editor only) Appears in an installation that is part of a Visual Studio solution Contains a list of files that result from projects that have been excluded from the current build configuration and therefore should not be included in the compiled .MSI WiseVSOutput (Visual Studio integrated editor only) Contains a list of...
Page 563: Appendix C Property Reference
Appendix C Property Reference Properties are variables that are used by Windows Installer during installation. This section lists Windows Installer properties. This chapter includes the following topics: Build Properties on page 563 INI File Properties on page 567 Run Time Properties on page 570 See also: Properties...
Page 564 Property Reference Property name Description _WiseDialogTitleFontDefault Contains the text style used for the titles on wizard pages. This is not for the text in the title bar itself, but for the text inside the wizard that introduces the page content. The font choices for this property are listed in the TextStyle table located on the Tables tab.
Page 565 Property Reference Property name Description MaintenanceMode Sets the initial value of the radio button on the Maintenance Welcome dialog. The default value, “Modify”, causes the Modify radio button to be marked by default. The Next button on the Maintenance Welcome dialog has events attached to it, which cause different pages to appear based on the radio button that is marked.
Page 566 Property Reference Property name Description WiseInitAdminError Contains the text of the error message that appears if the Windows Installer runtime needs to be installed but the current user does not have administrator privileges, which are necessary to install it. If an installation creates an .EXE that launches an .MSI, this property sets the default value for the AdminError property in the .INI file that’s generated.
Page 567: Ini File Properties
Property Reference Property name Description WiseInitProgressText Enter the text that should display while the hourglass is being displayed during installation. WiseInitSpaceError Contains the error text that is displayed if the destination computer does not have enough free disk space to copy the .MSI database to its local disk drive. If an installation creates an .EXE that launches an .MSI, this property sets the default value for the SpaceError property in the .INI file that’s generated.
Page 568 Property Reference Property name Description AdminError Contains the text of the error message that appears if the Windows Installer runtime needs to be installed but the current user does not have administrator privileges, which are necessary to install it. Defaults to the value of the build property named WiseInitAdminError.
Page 569 Property Reference Property name Description ProductCode ProductCode is a GUID (global unique identifier) generated by Windows Installer, that uniquely identifies this product. No product codes are alike. You can generate a new product code on the Product Details page. Do not enter new product codes, because they must be created according to a specific algorithm.
Page 570: Run Time Properties
Property Reference Property name Description WiseInitSuffix Text that displays after the “Wise Installation” text in the installations’s initialization window. The initialization window is the small window that appears before the installation wizard dialog boxes appear. This defaults to the value in the build property WiseInitSuffix. Build Properties on page 563.
Page 571 Property Reference Property name Description <VIRTDIR >_HOMEDIR Contains the physical home directory of the virtual directory. <VIRTDIR>_BEGINURL Contains the beginning portion of the URL of the virtual directory. <VIRTDIR>_URL Contains the URL of the virtual directory. <WEBSITE>_BEGINURL Contains the beginning portion of the URL of the web site. Example: To create a shortcut to a specific page in the Web site, use: [<WEBSITE>_BEGINURL]file_name.html <WEBSITE>_HOMEDIR...
Page 572: Index
Index Symbols copy and paste 498 specifying 104 deleting 496 ApplicationUsers 564 .NET dialog box 496 ApplicationWatch 392 about 549 in component rule 58, 63 ASP user properties 570 APPS_TEST 564 in debugger 487 assembly options 40 ASPNET_USER 570 in installation sequence 495 file attributes 149 standard 496 assembly...
Page 573 auto-updating 436 from installed file 519 patch, removing 259 editing 436 from property 520 public property, changing 258 missing file 123 tips 507 repair 257 storing .DLL 514, 516 running 100, 251 Call VBScript storing .EXE 526 testing 99 from embedded code 521 storing .MSI 529 transform, applying 258 from installation 521...
Page 574 component error, add to Task List 26 where to use 437 properties 542 report 544 Component Object Model 285 Condition Builder 441 restrictions on placement 497 component rules configurable data 375 run level 503 about 58 configurable merge module run on uninstall 506 action 58, 63 Also see merge module run once 506...
Page 575 DefaultUIFont 564 DiagnosticSecurityCheckFileWrite 555 setting as default 467 sizing 471 deferred execution 542 DiagnosticSecurityCheckRegistryRead spacing 471 deferred mode state, setting 438 about 495 DiagnosticSecurityCheckRegistryWrite tab order, setting 472 accessing properties 509 text 463 DelayReboot 568 dialog box tooltip, adding 467, 469 about 449 Delete button, unavailable 25 types 461...
Page 576 sending parameters to 508, 515, event features tree 111 517, 517 dialog box control 466 including in media 240 shared DLL count 141, 426 macro 483 installation location 118 Windows Installer method 508, installation options 114 event macro 516, 517 installation state 538 about 484 moving 111...
Page 577 removing from destination showing 486 details 276 computer 142 installing to 266 removing from source control 353 required version, setting 189 removing when invalid 409 restarting 269, 271 searching for 192 user for ASP 570 See Global Assembly Cache self-registration 147, 148 version 564 General Information page 108 short file name 216...
Page 578 creation options 84 installing 390 transform, creating 290 custom 117, 203 product code 389 language ID debugging 487 InstMSI CmdLine 568 list 310 disconnected 96 setting 295, 298 InstMsi3.exe 234 displaying images during 472 Language menu, using 305 integer in condition 439 execution of actions 487 Language Pack 309 interface 18...
Page 579 creating 483 custom action 39 minimum installer version 416 editing 483 dependency, adding 367 minimum system requirements event 484 directory for downloads 382 See system requirements running 484 directory, default 32, 48 Minor upgrade 334 downloading from Web or CD 34 Macro Editor mixed installation 40, 105 exclusion, adding 368...
Page 580 Also see merge module .NET assemblies 40 template-specific 22 defined 68 about 37 Palm add-on folder advertising 41 MSP file about 248 digital signature 43 Also see patch installing to 250 general 38 defined 69 Palm OS Installation Expert 47 how created 335 about 248 merge modules 48...
Page 581 PATCHWIZ.DLL 335 PRIMARYFOLDER 565 how they are set 445 INI file 567 path private assembly 138, 550 initializing 445 Also see source path private key 43, 263, 343, 343 installation project 85 broken 359, 409 private key file 262, 342 masking user entry 481 changing directories 360 privileges...
Page 582 32-bit or 64-bit view 163 removable media, copying run installation data type 169 installation 318 changes not saved 100 empty key, adding 163 how to 99 remove from destination computer exporting 166 in virtual layer 99 file 142 for elevated privileges 170 with command line 100 registry entry 165 for multiple users 170...
Page 583 colors of actions 496 editing 174 SpaceError 569 commenting out line 498 shortcut, mobile device 247 SPC file 262, 342 how they are run 495 Shortcuts page 172 SQL Client Tools 478 inserting blank line 534 side-by-side sharing 137, 550 SQL Connection dialog box restricted areas 497 about 451...
Page 584 removing 221 target computer Test event macro 485 resetting 221 See destination computer text box synchronous, defined 543 target platform dialog box control 462 about 70 resizing for language 304 syntax, check macro for 486 default 18 text strings SYS file 179 feature 116 Also see language system context 495, 543...
Page 585 compiling to language about 200 views 18 transform 290 disabling 79, 198 Virtual Directories page of progress text 567, 569 enabling 198 See Web Files page of user interface 287 preventing in WiseScript custom virtual directory strings, See text strings action 503 changing to Web site 273 translator, ODBC...
Page 586 Web Files page 266 about 545 adding files from 133, 153 about 125 actions 496 connecting to 65 when to use 127 administrative installation 317 options 50 comparing files 93 Web folder Wise Standard.msi 460 compatibility with 109 creating 273 Wise tables 559 database 68 details 276...
Page 587 WiseLangString table 560 WiseSourcePath table 561 working with 70 WiseLanguage table 560 WiseSql1.sql 280 WSM file Also see merge module WiseLaunchCondition table 560 WiseSQLCallDLL 557 defined 68 WiseMaskedProperties 567 WiseStartup 557 WSPROJ file 68 WiseMediaOptions table 398, 560 WiseStreamFiles table 561 wwwroot 267 WiseMetaDataCache table 560 WiseTaskList table 561...

This manual is also suitable for:

Windows installer editor 7.0 sp2

Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Technical Support

Chapter 1: Introduction

Chapter 2: Setting up

Chapter 3: Working with Wise Installation Files

Chapter 4: Defining an Installation Project

Chapter 5: Assembling an Installation

Chapter 6: Your Installation on the Destination Computer

Chapter 7: Organizing Your Installation into Releases

Chapter 8: Advanced Installations

Chapter 9: Translating an Installation

Chapter 10: Distributing an Installation

Chapter 11: Upgrading Applications

Quick Links

Troubleshooting

Related Manuals for Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0

Summary of Contents for Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0