Getting Started Guide

Wise for Windows Installer Getting Started Guide
Notice
Wise for Windows Installer, version 6.2 1994-2005 Wise Solutions, Inc. All Rights Reserved. This documentation and the accompanying software are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any human or computer language without prior written permission of Wise Solutions, Inc. Wise Solutions, Inc. asserts its Moral Right to be identified as the author of this work, in all jurisdictions which recognize the Moral Right. Unless otherwise provided by written agreement with Wise Solutions, Inc., this publication, and the software sold with this publication, are provided as is without warranty of any kind either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The entire risk arising out of the use or performance of this publication and software remains with you. In no event will Wise Solutions, Inc., or any of its suppliers, be liable for any lost profits, lost savings, direct, incidental or indirect damages or other economic or consequential damages, even if Wise Solutions, Inc., or its suppliers, have been advised of the possibility of such damages. Wise Solutions, Inc. reserves the right to modify this document at any time without obligation to notify anyone. In no event shall Wise Solutions, Inc.s or its suppliers liability under this agreement exceed the sum of any amounts paid hereunder by the customer to Wise or the supplier. Wise Solutions, Inc. owns a number of trademarks and service marks (the Marks). These Marks are extremely valuable to Wise Solutions, Inc. and shall not be used by you, or any other person, without Wise Solutions, Inc.s express written permission. The Marks include, but are not necessarily limited to the following: Application Isolation Wizard; ApplicationWatch; ConflictManager; ExpressBuild; Installation Development Life Cycle; InstallBuilder; InstallMaker; InstallManager; InstallTailor; MSI Debugger; MSI Script; PackageManager; Preflight Deployment; SetupCapture; SmartMonitor; SmartPatch; Software Distribution Made Easy; Software Installations Made Easy; Unwise; Virtual Capture; Visual MSIDiff; WebDeploy; Wise Installation System; Wise MSI Editor; Wise Package Studio; Wise Software Repository; Wise Solutions; WiseScript; WiseScript Express; WiseUpdate; WiseUser; and the Wise Solutions logo. In addition to Wise Solutions, Inc.s Marks, some Wise Products may include Trademarks or Service Marks owned by other corporations. These other Marks include, but are not necessarily limited to Microsoft Windows and Microsoft Visual Studio .NET, which are registered Trademarks of Microsoft Corporation. You shall not use any of the Trademarks or Service Marks of Wise Solutions, Inc., Microsoft Corporation, or any other entity, without the express written permission of such Trademark or Service Mark owner. Wise Solutions, Inc., a wholly owned subsidiary of Altiris, Inc. 47911 Halyard Drive; Plymouth, Michigan 48170 USA Phone: +1 734 456 2100 Fax: +1 734 456 2456 www.wise.com
Contents
Chapter 1: Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Getting Help and Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Getting Updates Over the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 2: Configuration Best Practices for the Enterprise Edition . . . . . . . . . . . . . . . . . 9

Dedicated SQL Server Configuration . . . . . . . . . . . . . . . . . . . . . . . Single Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Wise for Windows Installer Configurations . . . . . . . . . . . Upgrading an Unsupported Wise for Windows Installer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 11 12 13
Chapter 3: Installing Wise for Windows Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Install Enterprise Edition . . . . . . . . . . . . . . . . . . Choosing the Location for the Share Point Directory . . . . Authentication Best Practices . . . . . . . . . . . . . . . . . . . . . . . Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Standard and Professional Editions . . . . . . Installing the Enterprise Edition . . . . . . . . . . . . . . . . . . Installing the Wise for Windows Installer Language Pack . Starting the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering Your Software . . . . . . . . . . . . . . . . . . . . . . . . . Converting an Evaluation Version to a Production Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 17 17 18 19 20 21 23 24 24 24
Chapter 4: Managing the Wise Software Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

About the Wise Software Repository . . . . . Accessing the Wise Repository Manager . . The Wise Repository Manager Interface . . Configuring the Wise Software Repository . Upgrading Databases . . . . . . . . . . . . . . . Registering a Database . . . . . . . . . . . Changing Database Settings . . . . . . . . . . Creating Software Manager Databases . . . Creating a New Repository . . . . . . . . . . . Opening a Repository . . . . . . . . . . . . . . . Repository Configuration Dialogs . . . . . . . Setting the Wise Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 27 28 29 30 31 31 31 32 32 33 35
Chapter 5: Basic Tutorial: Creating an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Create a New Installation Project . . . . . . . . . . . . . Open a Project and Set Options . . . . . . . . . . . Enter Product Details and General Information. Create and Organize Features . . . . . . . . . . . . Assemble the Installation . . . . . . . . . . . . . . . . . . Add Files to the Installation . . . . . . . . . . . . . . Add Registry Keys . . . . . . . . . . . . . . . . . . . . Add a Shortcut . . . . . . . . . . . . . . . . . . . . . . . Create a File Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 37 38 39 40 40 42 43 43
Customize the Installations Behavior on the Destination Computer . . Set System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Dialogs That Appear to End Users . . . . . . . . . . . . . . . . . . Configure Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . Define Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customize the Demo Release Properties . . . . . . . . . . . . . . . . . . Compile and Test the Installation . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. ..
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
44 44 44 45 45 46 47 48
Chapter 6: Advanced Tutorial: Using MSI Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Call a .DLL With a Custom Action . . . . Set a Directory With a Custom Action . Call an .EXE With a Custom Action . . . Performing Advanced Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 54 57 60
Chapter 7: Tutorial: Visual Studio Integrated Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Open the C# QuickFacts Solution and Create an Installation Project . Open the Installation Project and Set Options . . . . . . . . . . . . . . . . Enter Product Details and General Information. . . . . . . . . . . . . . . . Add Files to the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 63 63 64
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Chapter 1
Welcome
Wise for Windows Installer is an installation development system for creating and editing Windows Installer (.MSI) installation packages. It is a complete and userfriendly front end for generating Windows Installer database files, which are executed by the Windows Installer engine. With Wise for Windows Installer, you can: Create installations that are compliant with Microsofts Windows 2000 logo program. Edit and refine installations that youve converted from other formats. Import development projects. Through its Visual Studio integrated editor, Wise for Windows Installer offers a complete, seamless integration of the entire installation authoring environment directly into the Microsoft Visual Studio .NET development environment. This tight integration allows for automatic synchronization of your development project with your installation, saving you time and significantly improving the quality of your installations. Microsoft Windows Installer is a Microsoft technology that provides a standard installation engine that can be used for the installation of any 32-bit or 64-bit Windows software product. It resides on the destination computer and performs the installation of applications. Windows Installer technology provides features that are not available in traditional installation-building products (examples: self-healing and install-ondemand). Topics include: Documentation Roadmap. Getting Help and Product Support. How to Check Online Help. Getting Updates Over the Web.
Documentation Roadmap
The Wise for Windows Installer documentation assumes that you are proficient in the use of the Windows operating system. If you need help using the operating system, consult its user documentation. Use the following sources of information to learn the product.
Online Help
The online help contains detailed technical information and step-by-step instructions for performing common tasks. For details on using help, see Check Online Help on page 6.
Welcome
Reference Manual
All the material in the online help is also available in .PDF-format reference manuals. Reference manual .PDFs are provided for Wise for Windows Installer and WiseScript Express. The Enterprise Edition also includes a Software Manager reference manual. To access the .PDF reference manuals, select Help menu > Reference Manual from within each product. (In Visual Studio: Help menu > Wise Help > Reference Manual.)
Getting Started Guide

The printed Getting Started Guide contains system requirements, installation instructions, and a tutorial. To access a .PDF version of the Getting Started Guide, select Help menu > Getting Started. (In Visual Studio: Help menu > Wise Help > Getting Started.) The installation and repository management sections of the Getting Started Guide are also available as online help. In the Wise Repository Manager, select Help menu > Help Topics.
Windows Installer SDK Help

You can get technical details about Windows Installer from its own help system, which is written by Microsoft for a developer audience. In Wise for Windows Installer, select Help menu > Windows Installer SDK Help. (In Visual Studio: Help menu > Wise Help > Windows Installer SDK Help. Windows Installer SDK help topics are also available within the Visual Studio .NET help collection.)
Release Notes
A release notes document, in .HTM format, covers new features, enhancements, bug fixes, and known issues for the current version of this product. It also contains links to release notes for other versions. Access the release notes in the following ways: Browse the product CD. Select Help menu > Release Notes. (In Visual Studio: Help menu > Wise Help > Release Notes.) If you are a registered customer, visit http://support.wise.com to enter the Support Center, and then click the Downloads link.
Getting Help and Product Support

Many resources are available to help you use our products. You can search the product help or reference manual .PDF for answers, or you can use one of the many support resources available to you as a registered customer. Also see Documentation Roadmap.
Check Online Help

Access help in the following ways: To display context-sensitive help for the active page or dialog, press F1. To select a help topic from a table of contents, index, or search, select Help menu > Help Topics. (In Visual Studio: Help menu > Wise Help > Help Topics.)
Welcome
Select other commands from the Help menu to view the Windows Installer SDK Help, to view the .PDF-format reference manual or getting started guide, to view Wise resources on the Web, or to check for upgrades. If you need help and cannot find the answer in the documentation, explore our technical support options below.
Use the Technical Support Center

Registered customers can use the Technical Support Center, located at http:// support.wise.com, to submit online support requests, register products, manage customer information, download updates, or search the Knowledgebase. The Knowledgebase contains how-to procedures, answers to common support questions, and workarounds.
Visit Our Newsgroups

Visit www.altiris.com/support/forum/default.asp. Newsgroup postings by your peers contain answers, tips, analysis, and other comments. Contribute your own expertise to help others.
Subscribe to TechInfo
TechInfo is a free e-mail newsletter that contains technical tips, product updates, and other important technical information. To subscribe or to read back issues, visit www.wise.com/techinfo.asp.
Ask Our Support Team

If you cant find an answer in our online resources, you can obtain support by phone or online at http://support.wise.com. Flexible payment options are available to meet your support needs. For additional details about our support services, visit www.wise.com/ supportoptions.asp or call 1-734-456-2600. Before you contact technical support, obtain the following: Serial number and product version, which you can find by selecting Help menu > About. Operating system version and service pack version if applicable. A description of what you do before the problem occurs. The text of any error messages that appear. Your name, company name, and how to contact you. Contract number or payment information, if applicable.
Take Advantage of Our Consulting and Training Services

When you have a challenging repackaging or installation problem, our consultants can help with script writing, repackaging, installation development, and other solutions that are fully customizable to fit your project and budget. Visit www.wise.com/consulting.asp for details. To upgrade your installation and packaging skills, consider training. Our certified instructors draw from practical experience to provide relevant course content. Visit www.wise.com/training.asp for course descriptions and schedules.
Welcome
Contact Our Sales Department

Contact our Sales department to purchase additional products, upgrades, support services, or consulting and training services. U.S.: +1 800 554 8565 EMEA: +8000 ALTIRIS (2584747) or +49 211 68 773 222 Other International: +1 734 456 2100 E-mail: wisesales@altiris.com Web Site: www.wise.com/ordercentermain.asp
Getting Updates Over the Web

You can get the latest version of Wise for Windows Installer using your active Internet connection. Minor point releases (x.01, x.02, and so on) are generally free, while major number releases generally incur an upgrade fee. Point releases generally contain maintenance updates such as bug fixes and minor feature additions.
To check for updates:

1. 2. Connect to the Internet. In Wise for Windows Installer, select Help menu > Check for Updates. A confirmation prompt appears, and then you are connected to the Technical Support Center Web site. If you have not registered this product, follow the screen prompts to create a user account and register. You will need a valid product serial number. After you complete the registration, click the link to enter the Technical Support Center. If you have registered this product, log on and then click the link to enter the Technical Support Center. 3. Click the Downloads link. Follow the instructions on the Web page to download the appropriate update.
Note Wise for Windows Installer can remind you to check for updates. Select an option in the Check for Updates drop-down list in Wise Options. This sets the frequency at which you will be reminded to check for updates.
Chapter 2
Configuration Best Practices for the Enterprise Edition

Enterprise Edition only.
Installing the Standard and Professional Editions of Wise for Windows Installer is relatively simple; they can be installed in one basic configuration only and typically are installed by a single user on their local computer. When you install Wise for Windows Installer - Enterprise Edition in a multi-user environment, you have several options for configuring the installation. This section describes the configurations that are supported. Review these configurations before you install Wise for Windows Installer. One important change from previous versions is that the share point directory must reside on the same computer as the Wise for Windows Installer application files. Versions of Wise for Windows Installer earlier than 6.2 did not enforce this. If you are upgrading to 6.2 or later, and your share point directory is not on the same computer as Wise for Windows Installer, see Upgrading an Unsupported Wise for Windows Installer Configuration on page 13. Topics include: Dedicated SQL Server Configuration. Single Server Configuration. Additional Wise for Windows Installer Configurations. Upgrading an Unsupported Wise for Windows Installer Configuration.
Dedicated SQL Server Configuration

Wise Server
SQL Server
Clients
Computer
Wise for Windows Installer Server Dedicated SQL Server
What to Install
Wise for Windows Installer server Share point directory SQL Server Wise for Windows Installer databases
Clients
Wise for Windows Installer client
10
Single Server Configuration

Enterprise Edition only. Small Team
Wise/SQL Server
Clients
Computer
Dedicated Server
What to Install
Wise for Windows Installer server Share point directory SQL Server (for client support) or MSDE (local computer use, non-client support) Wise for Windows Installer databases
Clients
Wise for Windows Installer client
Single User
Recommended environment: Single user with no expected growth. This configuration is not scalable.
Wise/SQL Server
Computer
Dedicated Server
What to Install
Wise for Windows Installer server Share point directory SQL Server (for client support) or MSDE (local computer, non-client support) Wise for Windows Installer databases
Clients
no clients
11
Additional Wise for Windows Installer Configurations

After you have determined which of the supported Wise for Windows Installer configurations is best for your environment, decide whether you need to support multiple Wise Software Repositories or databases.
Multiple Wise Software Repositories

In a large enterprise with multiple teams, each team might use a different share point directory and Wise Software Repository. Because a Wise for Windows Installer server can be associated with only one active repository at a time, each team must install their repository on a different server. Members of one team can subscribe to packages in a Software Manager database that is managed by another team. In the example below, each team has subscribed to packages in the other teams Software Manager database.
Team 1 subscribes to Team 2s Software Manager database
Team 2 subscribes to Team 1s Software Manager database
Team 1 Server
Team 2 Server
Team 1 Clients Team 2 Clients
Note For ease of illustration, the single server configuration is shown. This concept also works with the other recommended Wise for Windows Installer configurations.
Multiple Software Manager Databases

You might want to use multiple Software Manager databases in these instances: If you import a large number of applications for a large organization, you can use multiple databases to reduce the database size. If your organization develops a large number of unrelated applications, you can use separate databases to group them. This concept is similar to using package groups, but on a larger scale. Each database should reside on its own server. Running multiple databases on a single server degrades performance. In addition, you cannot run the Wise scheduled tasks,
12
which import packages and refresh package subscriptions on a server-based installation, on more than one database on a single computer.
SQL Server 1
Software Manager database 1
SQL Server 2
Software Manager database 2
Wise Server
Share point directory
Clients
Upgrading an Unsupported Wise for Windows Installer Configuration

Although it was not recommended, previous versions of Wise for Windows Installer allowed the share point directory and the Wise for Windows Installer installation to be on different servers. With the release of Wise for Windows Installer 6.2, this configuration is not supported because the Wise Task Manager, a service that performs various background operations (example: the upgrade process), requires the share point directory and the Wise for Windows Installer installation to be on the same server. If you currently have this configuration, you cannot simply move the share point directory. Instead: 1. Install Wise for Windows Installer server on the computer that contains the share point directory. The server installation does not use up a license unless someone actually uses Wise for Windows Installer on that computer. On each client computer, access the Wise Options dialog > Repository tab and verify that the share point directory on the new Wise for Windows Installer server is specified.
2.
13
Before Wise/SQL Server

Wise for Windows Installer Wise databases * * Can also reside on separate servers
File Server
Share point directory
Clients
After
Wise for Windows Installer server is on the computer that contains the share point directory. The Wise for Windows Installer clients use the share point directory on the new Wise for Windows Installer server.
SQL Server
Wise databases * * Can also reside on separate servers
Wise Server
Share point directory Wise for Windows Installer
Clients
14
Chapter 3
Installing Wise for Windows Installer

Refer to the information in this section to get Wise for Windows Installer installed and running. Topics include: The System Requirements for installing Wise for Windows Installer. Information to gather Before You Install Enterprise Edition. Authentication Best Practices. Installation Options. Instructions for installing the various configurations of Wise for Windows Installer: Installing the Standard and Professional Editions. Installing the Enterprise Edition. Installing the Wise for Windows Installer Language Pack. Starting the Software. Registering Your Software. Converting an Evaluation Version to a Production Version.
System Requirements
Note Wise for Windows Installer cannot be installed on any computer that contains Wise for Visual Studio .NET or Wise Package Studio (any edition or version). The Visual Studio integrated editor requires Microsoft Visual Studio .NET (any edition). For Microsofts requirements for installing Visual Studio .NET, consult the documentation that you received with Visual Studio .NET.
Requirement
Computer/processor Operating system
Value
PC with a Pentium II-class processor, 450 MHz Windows 2000 or later (SP4 recommended) Windows XP Professional (SP2 recommended) Windows Server 2003
15
Requirement
Internet Explorer
Value
5.5 or later or later* * Software Manager reports require 6.0 or later, or Microsoft XML Parser (MSXML) 3.0 Service Pack 7.
RAM Drive Display Free space on boot drive Free space on installation drive Network (Enterprise Edition only) Database (Enterprise Edition only)
128 MB; 256 MB recommended CD-ROM or DVD-ROM drive Super VGA (800 x 600) or higher-resolution monitor with 256 colors 65 MB 120 MB Windows-based network environment Your environment must contain at least one server that has one of the following: Microsoft SQL Server (English version only). Version 7.0 required; 2000 recommended. SQL Server 2005 and SQL Server 2005 Express are supported. Microsoft Data Engine (MSDE). MSDE does not support Wise for Windows Installer client installations. If you will install Wise for Windows Installer in a client-server configuration, use SQL Server. If you are upgrading from a previous version of Wise for Windows Installer that used Access databases, the Wise Repository Manager will upgrade the databases to SQL Server or MSDE.
Installations that you create with Wise for Windows Installer can be run on any Windows operating systems that are supported by Windows Installer. Windows 95 and earlier versions of Windows NT 4.0 do not contain Windows Installer software by default, so if you plan to run an installation on those operating systems, configure it to pre-install Windows Installer. To do so, use the option provided in Installation Expert > Prerequisites page.
.NET Framework System Requirements

The .NET Framework is required for advanced .NET support in Wise for Windows Installer. The .NET Framework requires Microsoft Internet Explorer 5.01 or later and one of the operating systems supported by Wise for Windows Installer.
16
Before You Install Enterprise Edition

Wise for Windows Installer - Enterprise is a multi-user, team-based product, which lets you install in such a way that you can share data with other users and other applications. Note Wise for Windows Installer cannot be installed on any computer that contains Wise for Visual Studio .NET or Wise Package Studio (any edition or version). You might need to gather information, from a team leader, system administrator, database administrator, or other team members, that will enable you to install correctly for your environment. Have serial numbers available during installation. If this is an upgrade, you also need the serial number of the previous version. To find this, open the previous version of Wise for Windows Installer and select Help menu > About. Find out what share point directory to use. In a multi-user environment, the share point directory must be on a shared network drive. All users in a workgroup must specify the same share point directory during installation. This lets all users access the same application data and shared resources. See Choosing the Location for the Share Point Directory. Obtain the following information about the databases you are using: The server name that contains the database and the authentication method (NT or SQL Server) that the database uses. Whether the database has been created or whether you need to create it during installation. If it does not exist or needs to be upgraded, you need database administrator privileges to create or upgrade it. So that you can create databases, either your currently logged on user profile must have database administrator privileges on the database server, or you must have the SQL user name and password of a database administrator available. If you plan to use a SQL Server or MSDE database server that uses SQL Server authentication, you will need to create users during installation. These users will have access to the database you create. You need to know what user IDs to create.
Choosing the Location for the Share Point Directory

You can use a share point to enable team-based features of Wise for Windows Installer Enterprise. The recommended location of the share point directory depends on your environment.
Where to Locate the Share Point Directory

The share point directory must reside on the same computer as the Wise for Windows Installer application files. Versions of Wise for Windows Installer earlier than 6.2 did not enforce this. If you are upgrading to 6.2 or later, and your share point directory is not on the same computer as Wise for Windows Installer, see Upgrading an Unsupported Wise for Windows Installer Configuration on page 13.
17
Environment
Single user Team, sharing project files
Share Point Location

Local or network directory. Shared network directory accessible to team members. In a large enterprise with multiple teams, each team might have a different share point directory.
When the share point directory is on a shared network drive, all users in a workgroup must specify the same share point directory during installation. This lets all users access the same application data and shared resources.
How is the Share Point Directory Created?

During the initial Wise for Windows Installer server installation, the share point directory is created and shared by the Wise Repository Manager. During a client installation, a new share point directory is not created. Instead, you must specify the share point directory that was configured during the server installation. During creation of a new Wise Software Repository, the share point directory is created and shared by the Wise Repository Manager.
Authentication Best Practices

For each Wise for Windows Installer database (Software Manager and Wise Services), you can: Specify the logon information for a database administrator (DBA). Define how user names and passwords should be validated: You can use either SQL Server or Windows NT authentication.
Environment
Client users have local NT accounts. Client users have a domain account on the SQL server, and have read and write permissions.
Authentication Method
SQL Server only (recommended). Windows NT or SQL Server.
If you have installed SQL Server or MSDE with NT authentication only, the Wise Task Manager, which manages certain Wise for Windows Installer operations, will not work. Therefore, during the Wise for Windows Installer database configuration, the authentication method is changed to mixed mode (NT and SQL). If you have any questions about how this change affects SQL Server security, ask your database administrator.
18
Installation Options
You can install different editions and configurations of Wise for Windows Installer.
Standard and Professional Editions

Standard Edition is a Windows Installer and .NET installation authoring tool for professional software developers who want basic but robust support for creating Windows Installer and .NET installations. Professional Edition is a Windows Installer and .NET installation authoring tool for professional software developers who want to create installations for the next generation of applications, including desktop, server, Web, and mobile devices. The Standard Edition can be installed in one basic configuration only. It typically is installed by a single user on their local computer. See Installing the Standard and Professional Editions on page 20.
Enterprise Edition
Enterprise Edition is a Windows Installer and .NET installation authoring tool supporting organizations that develop multiple applications that share common resources. It helps professional developers create installations that adhere to their organizations standards, thereby decreasing the risk of deployment errors. The Enterprise Edition has 2 installation types: Server The server installation includes the share point directory and the Wise for Windows Installer databases. In a single-user environment, you can install the Enterprise Edition on your local computer. In effect, your local computer is the server. We recommend that you do this only if you do not plan to add users in the future. In the more typical group environment, you run the server installation on a shared network location. Then, you run the client installation on individual users computers. Client The client installation uses the share point directory and Wise for Windows Installer databases that are installed on the server. You install the Wise for Windows Installer program files on the client computer. See Installing the Enterprise Edition on page 21.
Wise for Windows Installer Upgrade

To upgrade from a previous version of Wise for Windows Installer: 1. 2. (Enterprise Edition only.) Back up the existing share point directory and Wise for Windows Installer databases. Run the installation and, on the User Information dialog, enter a new serial number and the previous version serial number. If you dont know the previous version serial number, open Wise for Windows Installer and select Help menu > About. The serial number appears on the About dialog. If Wise for Windows Installer is not installed on your computer, look for the serial number on the product box, CD case, or registration card you received with your original purchase.
19
3.
(Enterprise Edition only.) The upgrade installation does not delete the existing share point directory, Wise for Windows Installer databases, or settings. After the installation finishes, open the Wise Repository Manager to upgrade the share point directory and databases. See Upgrading Databases on page 30.
Installing the Standard and Professional Editions

Starting the Installation
1. 2. Close any other applications that are running. Start the installation program: From a downloaded file: double-click the installation file. From the product CD: When you insert the product CD, a Welcome dialog appears. Click the button that installs Wise for Windows Installer. If the Welcome dialog does not appear, use Windows Explorer to browse to the CD, then open the file named Autoplay.exe. 3. 4. On the Welcome dialog, click Next. On the License Agreement dialog, read the license terms, mark I accept the License Agreement, and click Next. If you do not accept the license agreement, you cannot continue the installation. Complete the User Information dialog: Serial Numbers Product Enter a production or evaluation serial number for the Standard or Professional Edition. If you are upgrading from a previous version, you should have received a new serial number for the upgrade. Previous Version If you are upgrading from a previous version of Wise for Windows Installer, enter the serial number for the previous version. If you dont know the previous version serial number, open Wise for Windows Installer and select Help menu > About. The serial number appears on the About dialog. Language Pack If you purchased the optional Language Pack, enter its serial number. Install Evaluation Version Mark this to install an evaluation version without a serial number. Full Name, Organization Enter this identifying information. Register on the Internet If this checkbox is marked, you will be prompted to register at the end of installation. 6. Complete the remaining dialogs, which are described below.
5.
Wise for Windows Installer Evaluation dialog

This dialog appears only when you mark the Install Evaluation Version checkbox on the User Information dialog.
20
Mark the option for the edition of Wise for Windows Installer to install.
Wise for Windows Installer Location dialog

In Destination Directory, specify where to install the Wise for Windows Installer application files.
Ready to Install the Application dialog

Click Next to start installing.
Final dialog
When the installation finishes, a dialog indicates that the installation has been completed successfully. On the final dialog, click Finish to exit the installation. If you chose to register on the Internet and you have an active connection to the Internet, your browser opens to product registration instructions on the Wise Web site. If you are prompted to restart your computer, do so.
Installing the Enterprise Edition

Starting the Installation
1. 2. Close any other applications that are running. Start the installation program: From a downloaded file: double-click the installation file. From the product CD: When you insert the product CD, a Welcome dialog appears. Click the button that installs Wise for Windows Installer. If the Welcome dialog does not appear, use Windows Explorer to browse to the CD, then open the file named Autoplay.exe. 3. 4. On the Welcome dialog, click Next. On the License Agreement dialog, read the license terms, mark I accept the License Agreement, and click Next. If you do not accept the license agreement, you cannot continue the installation. Complete the User Information dialog: Serial Numbers Product Enter a production or evaluation serial number for the Enterprise Edition. If you are upgrading from a previous version, you should have received a new serial number for the upgrade. Previous Version If you are upgrading from a previous version of Wise for Windows Installer, enter the serial number for the previous version. If you dont know the previous version serial number, open Wise for Windows Installer and select Help menu > About. The serial number appears on the About dialog. Language Pack If you purchased the optional Language Pack, enter its serial number.
5.
21
Install Evaluation Version Mark this to install an evaluation version without a serial number. Full Name, Organization Enter this identifying information. Register on the Internet If this checkbox is marked, you will be prompted to register at the end of installation. 6. Complete the remaining dialogs, which are described below.
Wise for Windows Installer Evaluation dialog

This dialog appears only when you mark the Install Evaluation Version checkbox on the User Information dialog. Mark the option for the edition of Wise for Windows Installer to install.
Select Installation Type dialog

To install Wise for Windows Installer and the share point directory on a server, mark Server. To install Wise for Windows Installer on a local computer and connect to the share point directory on a server, click Client.
Wise for Windows Installer Location dialog

In Destination Directory, specify where to install the Wise for Windows Installer application files.
User Account for Wise Server-Side Service dialog

(Server installations only.) Wise for Windows Installer contains a service that manages background operations. This user account lets the service access information it needs to perform these operations. Also, this user account becomes the Wise for Windows Installer server administrator; to use the Wise Repository Manager, you must be logged on as this user. Note This account is based on the NT account of the currently logged on user. If you prefer to run the Wise service under a different account, then cancel the installation, log on with that account, and restart the installation. User (Read-only.) This defaults to the currently logged on user. It is the same as your Windows NT login. Password Enter the password of the currently logged on user. If this password changes, you must change it in the Wise Repository Manager. See Setting the Wise Service Account on page 35.
Wise Share Point Directory dialog

(Client installations only.)
22
Specify the share point directory that was configured during the server installation. Enter a shared network location in UNC (recommended) or mapped drive notation. (Example of UNC: \\SERVER_NAME\WISE SHARE POINT.) In a large enterprise with multiple teams, each team might have a different share point directory and Wise Software Repository. After installation, you can change the repository that a client installation connects to. See Setting Repository Options in the Wise for Windows Installer Help.
Ready to Install the Application dialog

Click Next to start installing.
Final dialog
When the installation finishes, a dialog indicates that the installation has been completed successfully. Client installation: On the final dialog, click Finish to exit the installation. Server installation: If you mark Launch Wise Repository Manager, the Create New Repository wizard starts when you click Finish. See Repository Configuration Dialogs on page 33. If you chose to register on the Internet and you have an active connection to the Internet, your browser opens to product registration instructions on the Wise Web site. (Server installation: If you marked the option to launch the Wise Repository Manager, both windows open.) If you are prompted to restart your computer, do so.
What to Do Next
(Server installations only.) Before you can use Wise Package Studio, you must configure the repository. See Configuring the Wise Software Repository on page 29.
Installing the Wise for Windows Installer Language Pack

The Language Pack is an add-on to Wise for Windows Installer. It provides pretranslated strings for 20 additional languages on the Languages page, which lets you effortlessly ship your installations in other languages.
Options for Installing the Language Pack

If you purchase the Language Pack at the same time you purchase Wise for Windows Installer, the Language Pack is installed with the main application. Enter the Language Pack serial number on the User Information dialog. If you purchase the Language Pack after you install Wise for Windows Installer, then install the Language Pack separately. a. b. When you purchase the Language Pack, you receive a serial number. Download the Language Pack installation file (WfwiLangPack.exe) from the Wise Web site or insert the original product CD into your CD drive and navigate to the LangPack.exe file. Run the installation from WfwiLangPack.exe. The installation process is an abbreviated version of the Wise for Windows Installer installation wizard. Enter
c.
23
the Language Pack serial number on the User Information dialog and click through the remaining dialogs.
Starting the Software

1. Select Start menu > Programs > Wise > Wise for Windows Installer. The New Installation File dialog appears. If it does not appear, select File menu > New. 2. To create a new installation project, select the Windows Application icon. The Windows Application icon lets you create a standard installation. 3. 4. 5. In the File type section, specify the type of file to create. (Professional and Enterprise Editions only.) If the Target Platform options appear, specify whether this installation is enabled for 32-bit or 64-bit platforms. Click OK. The new installation opens.
For details on creating other types of installations and installations within a Visual Studio .NET solution, see the Wise for Windows Installer Help.
Registering Your Software

It is very important that you register your software. Registering qualifies you to receive technical support via newsgroups and e-mail, plus notifications about future product upgrades. If you did not register your software online during installation, you may do so as follows: 1. 2. Connect to the Internet. Do either of the following: In Wise for Windows Installer, go to the Home page and click the link to Product Registration. In your browser, go to www.wise.com/product_registration.asp. Your browser opens to the Product Registration page on the Wise Web site. 3. 4. Click the Wise Technical Support Center link on the Web page and create a new user profile or log onto an existing user profile. Follow the instructions on the Web page to complete the registration.
Converting an Evaluation Version to a Production Version

You can convert an evaluation version of Wise for Windows Installer to a production version without uninstalling the product. 1. 2. 3. Purchase the product and obtain a production serial number. Start the Wise editor interface of Wise for Windows Installer and click Serial Number on the Evaluation dialog. Enter the production serial number and click OK.
24
The evaluation version is converted to a production version. When you start Wise for Windows Installer, the Evaluation dialog no longer appears. If the production serial number is for a different edition than the evaluation serial number, you must uninstall the evaluation version before you install the production version.
25
Chapter 4
Managing the Wise Software Repository

The Wise Repository Manager gives you control over database configuration and updates, and lets you see the changes that are made by database updates. The Wise Repository Manager provides a view of the Wise Software Repository and lets you perform the following tasks: Configuring the Wise Software Repository, which consists of the Wise share point and the databases that are associated with it. Upgrading Databases. Changing Database Settings. Creating Software Manager Databases. Creating a New Repository. Opening a Repository to upgrade it or make it the default. Setting the Wise Service Account. The Wise Repository Manager is available on the Wise for Windows Installer server only. Procedures in this section assume that you are familiar with creating databases and registering ODBC data sources. We do not offer technical support for MSDE or SQL Server. If you need help, ask your database administrator. Caution Do not modify Wise for Windows Installer databases outside of the Wise Repository Manager.
Additional topics include: About the Wise Software Repository. Accessing the Wise Repository Manager. The Wise Repository Manager Interface. Repository Configuration Dialogs.
About the Wise Software Repository

The Wise Software Repository is a collection of resources, and information about those resources, for all software developed and used by an organization. This scalable repository provides a centralized point for managing software packages at any stage of development. The Wise Software Repository consists of:
26
Share Point Directory Contains shared resources used to create Windows Installer installations. It also contains source files for packages in the Software Manager database. All Wise for Windows Installer databases are associated with a specific share point directory. Software Manager database Contains all software packages created by an organization. Package resources might be included also (examples: files, merge modules, registry keys). Wise Services database Stores data that is generated and used by various background operations (examples: package import, the upgrade process). A repository can contain only one Wise Services database.
Multiple Repositories
In a large enterprise with multiple teams, each team might use a different share point directory and Wise Software Repository. Because a Wise for Windows Installer server can be associated with only one active repository at a time, each team must install their repository on a different server. A single Wise for Windows Installer server can contain multiple repositories. However, only one repository can be active at a time. To change the active repository on a Wise for Windows Installer server, open the repository in the Wise Repository Manager. A Wise for Windows Installer client can connect to any Wise Software Repository that it can access. To change a clients default repository, use the Wise Options dialog > Repository tab and specify the share point that is associated with an active Wise Software Repository.
Accessing the Wise Repository Manager

Enterprise Edition only. Requirements
To use the Wise Repository Manager: You must be logged on to a computer that contains a Wise for Windows Installer server installation. You must be logged on as the Wise for Windows Installer server administrator, that is, the user account under which Wise for Windows Installer was installed.
To start Wise Repository Manager:

You can start Wise Repository Manager in either of 2 ways: At the end of the Wise for Windows Installer installation, mark the option to launch the Wise Repository Manager when the installation finishes. When the Wise Repository Manager is launched, the Create New Repository wizard starts. After the product is installed, select Start > Programs > Wise > Wise Repository Manager.
27
If the Wise Software Repository has not been configured, the Create New Repository wizard starts. For details on the Create New Repository wizard, see Repository Configuration Dialogs on page 33. Also see: The Wise Repository Manager Interface on page 28 Configuring the Wise Software Repository on page 29 Upgrading Databases on page 30 Changing Database Settings on page 31 Creating Software Manager Databases on page 31 Creating a New Repository on page 32 Opening a Repository on page 32 Setting the Wise Service Account on page 35
The Wise Repository Manager Interface

When the Wise Repository Manager opens, it displays the current repository.
Wise Repository Manager Left Pane
Database needs to be updated
The left pane contains a tree structure that represents: The databases that comprise the Wise Software Repository. If the repository contains multiple Software Manager databases, the default is displayed in bold type. Note The Subscriptions subfolder displays any databases that are subscribed to from the selected Software Manager database. To manage a subscribed database, open the repository that it is associated with. Click the top-level folder or a database icon to display help in the right pane. Click a specific database (in bold type) to display maintenance options in the right pane.
28
Wise Repository Manager Right Pane

Describes what the selected action does
Upgrade actions and their statuses
Lists the SQL scripts or command lines that the selected action runs
In the right pane, you can: Upgrade the database to a new version. See Upgrading Databases on page 30. Display a record of completed upgrade actions by clicking Show Log on the toolbar. Change the database settings. See Changing Database Settings on page 31.
Configuring the Wise Software Repository

After you install or upgrade Wise for Windows Installer, you must configure the Wise Software Repository. This consists of defining: The share point directory. The location of the various Wise for Windows Installer databases. The authentication method for each database.
To configure the Wise Software Repository:

1. Access the Wise Repository Manager. See Accessing the Wise Repository Manager on page 27. If the Wise Software Repository has not been configured, the Create New Repository wizard starts.
29
2. 3.
Step through the Create New Repository wizard. For details, see Repository Configuration Dialogs on page 33. If you have upgraded from a previous version of Wise for Windows Installer, upgrade the databases. See Upgrading Databases on page 30.
Upgrading Databases
When you upgrade Wise for Windows Installer, you must also upgrade the Wise for Windows Installer databases before you can use them with the new version. You do this in the Wise Repository Manager. Do this after you configure the repository with the Create New Repository wizard. The icon next to the database name in the left pane indicates that the database must be upgraded before it can be used. When the red X is removed from the icon, you can safely use that database with the current version of Wise for Windows Installer. This can occur before all upgrade actions have been completed. That is because the upgrade might contain background actions that do not have to be completed before users can begin using Wise for Windows Installer. To review the changes that the upgrade will make, click an action in the Actions list. Information about what that action does is displayed in the Description and Details sections. The Upgrade to 6.00 and Upgrade to 6.10 actions upgrade databases earlier than those versions to a baseline format, from which you can upgrade to 6.2 or any later version. (The baseline version that appears in the actions description does not necessarily correspond to any product version number.) Note If you are upgrading a repository that contained multiple Software Manager databases, or if one of the databases had a name other than the default name, register and upgrade those databases separately. See Registering a Database on page 31.
To upgrade the entire repository:

On the Wise Repository Manager toolbar, click Upgrade. This upgrades all databases that require upgrading.
To upgrade one database at a time:

1. 2. In the left pane of the Wise Repository Manager, click a database name (in bold type). Do either of the following: To run all uncompleted actions, click Run All. To run the upgrade actions individually, click the first uncompleted action in the list and click Run. (Uncompleted actions are indicated by a status of Pending.) Then repeat for subsequent actions. You cannot run the actions out of sequence.
30
When the upgrade is complete:

The database or databases are updated, the actions you ran are marked as completed, and a record of the upgrade actions is written to WiseAdmin.log. To display the most recent log, click Show Log on the toolbar.
Registering a Database
Do this when you upgrade a repository that contains multiple Software Manager databases. During the Create New Repository wizard, you can specify only one Software Manager database. Therefore, the other Software Manager databases are not registered.
To register a database:
1. 2. In the left pane of the Wise Repository Manager, click the Software Manager icon. On the toolbar, click Register. The Select Data Source dialog appears. This is a standard Windows ODBC connection wizard, which lets you connect to a database via an ODBC data source. 3. Connect to the database. If you need help, ask your database administrator. The database appears in the left pane of the Wise Repository Manager. 4. Upgrade the database. See Upgrading Databases on page 30.
Changing Database Settings

You can change logon settings for a Wise for Windows Installer database from the Wise Repository Manager. 1. 2. In the left pane of the Wise Repository Manager, click a database name (in bold type). Click Settings in the lower right of the right pane. The Change Database Settings wizard starts. 3. Complete the following dialogs: Database Administrator Logon Information dialog Database Service Logon Information dialog See Repository Configuration Dialogs on page 33.
Creating Software Manager Databases

If you plan to import a large number of packages, you might use multiple Software Manager databases to reduce the size of the individual databases. Use the Wise Repository Manager to create Software Manager databases.
31
The ability to create a database is disabled for the Wise Services databases because a repository can contain only one of that database. This procedure assumes that you are familiar with creating databases and registering ODBC data sources. We do not offer technical support for MSDE or SQL Server. If you need help, ask your database administrator. 1. In the left pane of the Wise Repository Manager, right-click the Software Manager icon and select Create New Database. The Create New Database wizard starts. 2. Complete the following dialogs: Database Identification dialog Database Administrator Logon Information dialog Creation Options dialog See Repository Configuration Dialogs on page 33. 3. To make this the default Software Manager database, right-click the database name in the left pane and select Set as Default. The default database name is displayed in bold type.
To provide an additional level of security, your database administrator can set permissions on tables in the new Software Manager database. This is not required, but is an option if you are concerned about unauthorized users changing database tables outside of Wise for Windows Installer.
Creating a New Repository

When you create a new Wise Software Repository, all links to the old repository are broken, but the data is not deleted. The new repository becomes the default for all Wise for Windows Installer clients that connect to this server. 1. In the Wise Repository Manager, select File menu > New. The Create New Repository wizard starts. 2. Complete the dialogs that appear. When you are asked to specify the share point directory, specify a share point path that resides under an existing location. See Repository Configuration Dialogs on page 33.
The new databases are created and associated with the share point directory you specified. To provide an additional level of security, your database administrator can set permissions on tables in the new databases. This is not required, but is an option if you are concerned about unauthorized users changing database tables outside of Wise for Windows Installer.
Opening a Repository
32
In a large enterprise with multiple teams, each team might use a different Wise Software Repository. However, a Wise for Windows Installer server can be associated with only one active repository at a time. To change the default Wise Software Repository for a server installation, open a new repository. Note To change the default repository for a client installation, use the Wise Options dialog > Repository tab and specify the share point that is associated with an active Wise Software Repository. See Setting Repository Options in the Wise for Windows Installer Help. If you upgrade from a previous version of Wise for Windows Installer that has multiple repositories, only one repository is upgraded. To upgrade the other repositories, you must open them and then upgrade them. 1. 2. In the Wise Repository Manager, select File menu > New. On the Wise Share Point Directory dialog, specify the share point that is associated with the repository you are opening and click Next. If the repository associated with that share point is at the current version, it opens in the left pane. If the repository associated with that share point has not been upgraded, additional dialogs appear. Complete the dialogs to configure the repository, and then upgrade the database. See Repository Configuration Dialogs on page 33 and Upgrading Databases on page 30.
Repository Configuration Dialogs

All or some of the repository setup dialogs appear when you: Configure the repository as part of a new or upgrade installation. Change database settings. See Changing Database Settings on page 31 Create a new Software Manager database. See Creating Software Manager Databases on page 31. Create a new repository. See Creating a New Repository on page 32. Open an existing repository that has not been upgraded. See Opening a Repository on page 32.
Wise Share Point Directory dialog

The share point directory stores data that can be shared by team members. Specify a shared network location. Your entry is converted to UNC notation. This directory is created and shared for you. If you are creating a new repository after the initial installation, you must specify a share point path that is shared. Valid paths for a new share point: C:\Wise Share Point 2 \\server\c$\Wise Share Point 2
33
Invalid path for a new share point: \\server\Wise Share Point 2 Note When you perform a server installation in a team environment, we recommend that you install the share point directory on the same physical drive that contains the Wise for Windows Installer application files.
File Share Name dialog

The share point directory must be accessible by other computers. Enter the name of the file share to associate with the share point directory.
Database Identification dialog

When you create a new repository, this dialog appears for each database that you are defining. When you change a databases settings or add a Software Manager database, this dialog appears for that specific database only. Database Name Specify the database name to create or connect to. If you are creating an additional database, use a unique name. Example: Software Manager Database 2. If you are upgrading from a previous version, do not accept the default name if the existing database has a different name. Enter the exact name of the existing database. Server Select the database server for the database you specified.
Database Administrator Logon Information dialog

When you create a new repository, this dialog appears for each database that you are defining. When you change a databases settings or add a Software Manager database, this dialog appears for that specific database only. For recommendations on which authentication method to use, see Authentication Best Practices on page 18. Specify the logon information for a database administrator (DBA) for the selected database server: Windows NT authentication using your current logon credentials SQL Server authentication using a DBA login and password When you select this, enter a valid Logon ID and Password. Define how user names and passwords should be validated: Windows NT authentication using the users Windows logon credentials SQL Server authentication using a logon ID and password supplied by the user When you select this, you must create users. Do this on the Create New Users dialog. If users will log on with the DBA credentials, you do not have to create users.
Database Service Logon Information dialog

This dialog appears only when you change an existing databases settings. This account is used to access this database from various background processes (example: the upgrade process). The initial Wise for Windows Installer installation creates this account and generates a random password. If you prefer to manage this password yourself, you can change it here. The password you enter will be encrypted.
34
Create New Users dialog

This dialog appears if you specify SQL Server authentication for users. The DBA logon information you entered earlier will be used to create database users that you specify on this dialog for all databases that are being created (Software Manager, Wise Services). These users will have modification privileges in all databases. For each user, enter a User Name and Password and click Add.
Creation Options dialog

If the database is not local or the database already exists (example: during an upgrade), this dialog does not appear. Import sample applications into Software Manager Import packages for sample applications into the Software Manager database. This option lengthens configuration time.
Setting the Wise Service Account

Wise for Windows Installer contains a service that performs various background operations (example: the upgrade process). This service requires a user account to access the information it needs to perform these operations. This user account is set up when Wise for Windows Installer is installed on the server. If the password for the user account changes, then this service will not work until the users password is updated in the Wise Repository Manager.
To update the user account password:

1. 2. In the left pane of the Wise Repository Manager, click the Wise Service icon. In the right pane, change the password of the user account that is displayed.
Also see Accessing the Wise Repository Manager on page 27.
35
Chapter 5
Basic Tutorial: Creating an Installation

This tutorial guides you through the creation of a Windows Installer installation. A sample application, QuickFacts, which is included with Wise for Windows Installer, provides a realistic practice scenario. The QuickFacts program is a simple text viewer. QuickFacts does not make system changes to your computer and is safe to install. This tutorial works with all editions of Wise for Windows Installer. If you have the Professional or Enterprise Editions, you might see additional fields that are not discussed in this tutorial. This tutorial takes about 45 to 60 minutes to complete. If you stop before finishing, save the installation and resume the tutorial at a later time. If you use Visual Studio integrated editor, first follow this basic tutorial using the Wise editor. Then follow the Tutorial: Visual Studio Integrated Editor on page 61, which contains procedures that are specific to the Visual Studio integrated editor. In this tutorial, you will use Installation Expert to: Create a new installation project. Build an installation. Customize the installations behavior on the destination computer. Define releases. Compile and test the installation. Note This tutorial does not cover details of Installation Expert Pages and dialogs. Press F1 on any page or dialog for context-sensitive documentation.
Before You Start

Install Wise for Windows Installer. For installation options and instructions, see Installation Options on page 19. We assume that you are following this tutorial for the first time. Follow the instructions in this tutorial exactly as presented; otherwise, your results can deviate from the information presented here. Caution If you have followed this tutorial previously, delete any files you might have created then. If you previously installed the QuickFacts sample application, uninstall it before proceeding with the tutorial.
Create a New Installation Project

In this section, you set options for using Wise for Windows Installer. You then create a new installation, enter descriptive information about it, and structure the features in the installation.
36
Tasks in This Section

Setting options. Creating a new installation project. Entering product details. Entering general information. Entering information for Add/Remove Programs. Setting up features.
Open a Project and Set Options

You use the Wise Options dialog to customize the behavior of Wise for Windows Installer for all installations you create. Windows Installer projects are comprised of features, and normally, you view folders and registry keys per feature. In this procedure, you open a new project and set options that let you view folders and registry keys for all features simultaneously, making it easier to see the installation as a whole. 1. Select Windows Start menu > Programs > Wise > Wise for Windows Installer. The first time you launch the software, the New Installation File dialog appears. If it does not appear, select File menu > New. 2. On the New Installation File dialog: a. b. Select the Windows Application icon. Mark Create .WSI or .WSM project file that can be compiled into an .MSI or .MSM. This option lets you work in a project file (.WSI), which describes and compiles the actual installation file (.MSI). (Professional and Enterprise Editions only.) If the Target Platform section appears, mark Create installation for 32-bit platform.
c. 3.
Click OK. A new project opens.
4. 5.
Select Tools menu > Options. On the Wise Options dialog, click the Installation Expert tab and mark the following options: View directories for all features on Files page This lets you see all directories in Installation Expert > Files page, regardless of what feature each directory was created for. View registry keys for all features on Registry page This lets you see a composite view of all registry keys in Installation Expert > Registry page, regardless of what feature the registry key was created for. Note To display context-sensitive help, press F1.
6. 7.
Leave the defaults for all other options. Click OK.
37
8.
Save the installation with the name QuickFacts.wsi.
Enter Product Details and General Information

To enter information about the installation, you use pages in the Project Definition page group in Installation Expert. 1. Click Installation Expert at the lower left of the application window. Throughout this tutorial, you will use pages in Installation Expert. The pages are listed in the left pane; they are organized in groups that are listed in the order in which you usually will use them. 2. Under the Project Definition page group on the left, click Product Details. The Product Details page appears, where you enter meta data that is used in the installation dialogs to identify the product to the end user who is installing it. 3. Enter this information in the Package Meta Data table: Product Name Enter: QuickFacts Manufacturer Enter your company name. Application Type (Professional and Enterprise Editions only.) Make sure this is set to Win32 (non .NET). Installation Target (Professional and Enterprise Editions only.) Make sure this is set to Windowsbased desktop/server PC. 4. Under the Project Definition page group on the left, click General Information. The General Information page appears, where you set the information that appears when the end user right-clicks the installation file in Windows Explorer and selects Properties. 5. Enter this information on the General Information page: Title Enter: QuickFacts Author Enter your name. 6. Under the Project Definition page group on the left, click Add/Remove Programs. The Add/Remove Programs page appears, where you enter information to support the capabilities of the Add/Remove Programs control panel. 7. Enter this information on the Add/Remove Programs page: Display in Add/Remove Programs list Make sure this is marked. Online Info URL Enter: No support provided. 8. Save the installation.
38
Now that youve entered basic information about the installation, you can define the features that provide structure to the installation.
Create and Organize Features

After entering product details and general information for a new installation, you should define its structure. To create the structure of an installation, you define: What features make up the application. How those features are presented to the end user during installation. What conditions must be true for portions of features to be installed. Determine features and conditions before configuring other aspects of the installation, because all other system changes (adding files, adding registry entries, and so on) that you define later must be associated with a feature. Many pages in Installation Expert have a Current Feature drop-down list that lets you set options on a per-feature and per-condition basis. The QuickFacts installation consists of 4 features. The feature named Core, which is always installed, contains the QuickFacts program and online help. The other features, Birds, Cats, and Dogs, are optional and contain fact files about those animals. Each will appear as an optional feature during the QuickFacts installation.
To create and organize features:

1. Under the Project Definition page group on the left, click Features. The Features page appears. A feature named Complete already exists, because every installation must contain at least one feature. 2. Double-click the Complete feature or select it and click the Details button. The Feature Details dialog appears. 3. Complete the dialog: Name Override the existing name by typing Core, and then press Tab. Title Enter: Core Parent Leave the default. Description Enter: QuickFacts program and help files Required Feature Mark this. Leave the defaults for the rest of the fields and click OK.
39
4.
Use the Add button to enter information for 3 additional features as shown in the following table.
Name and Title

Birds Cats Dogs
Parent
Select <None>. Select <None>. Select <None>.
Description
Facts about birds Facts about cats Facts about dogs
Required Feature
Leave the default. Leave the default. Leave the default.
The Features page should display 4 features; all features should be on the same level in the tree. If not, display the feature details and change the Parent field until all features are on the same level.
5.
Save the installation.
The installation is now set up and structured into features. In the next section, you add files and other system changes to the installation.
Assemble the Installation

In this section, you add files and other system changes to the installation. Use the pages in the Feature Details group in Installation Expert.

Adding files to the installation. Adding registry keys. Adding a shortcut. Creating a file association. Before performing these tasks, you must have set up an installation project by following the procedures in Create a New Installation Project on page 36.
Add Files to the Installation

On the Files page, you specify the directories and files that will be installed on the destination computer. You specify files per feature; the files that you add are installed on the destination computer only if the feature is installed. Because this installation has multiple features, be sure to specify the feature for which you are adding files. You do this by selecting it from the Current Feature drop-down list.
40
To add files to the Core feature:

1. Under the Feature Details page group, select the Files page. On the Files page, the upper 2 list boxes show the directories and files available to your computer, including your local drives, mapped drives, and local network. The lower 2 list boxes represent the directory structure and files to be installed on the destination computer. Note To display context-sensitive help, press F1. 2. 3. 4. From the Current Feature drop-down list, select Core. In the lower-left list box, select the Program Files directory and click New at the lower left of the window. On the Create New Folder dialog, enter QuickFacts and click OK. A directory named QuickFacts appears under the Program Files directory. 5. 6. In the lower-left list box, select the QuickFacts directory you created. In the upper-left list box, navigate to and select the Tutorial\QuickFacts subdirectory of the Wise for Windows Installer application directory. The files in the QuickFacts directory appear in the upper-right list box. 7. Make sure the QuickFacts directory is still selected in the lower-left list box. In the upper-right list box, select License.txt, QckFacts.exe, and ReadMe.txt and click Add File. The 3 files are added to the QuickFacts directory in the installation. 8. 9. In the upper-left list box, expand the QuickFacts directory and select the Help subdirectory. Make sure the QuickFacts directory is still selected in the lower-left list box, and click Add Contents.
10. On the Add Contents dialog, leave the defaults and click OK. The Help directory and its contents are added to the installation. 11. In the lower-left list box, expand the Windows directory and click the System32 subdirectory. 12. In the upper-left list box, click the System32 subdirectory under the QuickFacts directory. 13. Drag the file QFGUITAM.DLL from the upper-right list box to the lower-right list box. In the Current Feature drop-down list, the number (6) should appear next to the Core feature name. This indicates that the Core feature contains 6 files. This completes the file additions for the Core feature. Now add files to each of the remaining features.
To add files to the remaining features:

1. Add files to the Birds feature: a. From the Current Feature drop-down list, select Birds.
41
b.
In the lower-left list box, click the QuickFacts directory and click New. Name the new directory FactFiles and click OK. Note If the QuickFacts directory does not appear in the lower-left list box, select Tools menu > Options, click the Installation Expert tab, and mark the checkboxes for View directories for all features on Files page and View registry keys for all features on Registry page.
c. d.
In the upper-left list box, click the FactFiles subdirectory of the QuickFacts directory. In the upper-right list box, select the files: Birds.bmp Birds.qft
e. 2.
Click Add File to add the files to the lower-right list box.
From the Current Feature drop-down list, select Cats. Then add the following files to the FactFiles directory for this feature: Cats.bmp Cats.qft Because you selected View directories for all features on Files page in Wise Options, you can still see the FactFiles directory in the lower-left list box, even though you added it to a different feature.
3.
From the Current Feature drop-down list, select Dogs. Then add the following files to the FactFiles directory for this feature: Dogs.bmp Dogs.qft
4.
To see all the files you added to the installation for all features, select All Features (Modify/Delete only) from the Current Feature drop-down list. The number (12) should appear next to the All Features name, indicating that the installation contains 12 files. You can navigate through the installation directories in the lowerleft list box to see the files that you have added.
This completes the file entries for this installation.
Add Registry Keys

To specify the registry entries to be installed or edited on the destination computer, you use the Registry page. You can add registry keys and values manually, but for this tutorial, you import them from a registry file (.REG) that is provided. 1. Select the Registry page. The upper 2 list boxes show keys and values in your computers registry. The lower 2 list boxes represent the keys and values to be installed on the destination computer. Note To display context-sensitive help, press F1. 2. From the Current Feature drop-down list, select Core.
42
3. 4.
Click Add at the lower left of the window and select Import. On the Select Registry File to Import dialog, navigate to the Wise for Windows Installer directory, select Tutorial\QuickFacts\Registry File\QuickFacts.reg, and click Open. QuickFacts.reg contains all the registry keys required for QuickFacts.
5.
In the lower-left list box, right-click HKEY_CURRENT_USER and select Expand Children. This expands the subkeys that you just imported. You can click through the subkeys to see the values that have been added.
This completes the registry entries for this installation.
Add a Shortcut
1. 2. 3. 4. 5. 6. 7. Select the Shortcuts page. From the Current Feature drop-down list, select Core. Click Add at the right of the window. On the Shortcut Type dialog, make sure the File in the installation and Advertised options are marked and click Next. On the Shortcut File Selection dialog, select the QuickFacts directory in the left pane, select QckFacts.exe in the right pane, and click Next. On the Shortcut Destination Directory dialog, make sure the Programs directory under the Start Menu is selected, and click Finish. On the Shortcut Details dialog, change the Name field to QuickFacts and click OK.
A shortcut for QckFacts.exe is added to the installation and will appear under Program Files in the Start menu when the product is installed.
Create a File Association

You can associate file extensions with executables to determine which application to launch when the end user double-clicks a file with a certain extension. The QuickFacts application has its own extension for fact files: .QFT. 1. 2. 3. Under the Feature Details page group, select the File Associations page. From the Current Feature drop-down list, select Core. Click Add at the right of the window and select New. The File Association Details dialog appears. 4. 5. 6. 7. Click the Extension Details tab. Browse to the QuickFacts directory, select the file QckFacts.exe, and click OK. In Extension, enter: qft Leave the defaults for the rest of the fields and click OK. The extension .QFT is added to the installation. When an end user double-clicks a file with this extension on the destination computer, the QuickFacts application launches. 8. Save the installation.
43
The installation now contains files and other system changes that will be installed on the destination computer. In the next section, you determine how the installation behaves on the destination computer.
Customize the Installations Behavior on the Destination Computer

In this section, you determine how the installation behaves on the destination computer.

Setting system requirements. Selecting the dialogs that appear during installation. Configuring installation types. Before performing these tasks, you must have added information to the installation by following the procedures in Assemble the Installation on page 40.
Set System Requirements

You can specify minimum hardware and software requirements for the installation and set warning messages that appear to the end user if the destination computer does not meet specified requirements. 1. 2. Under the Target System page group, select the System Requirements page. On the System Requirements page, double-click Windows Version. The Windows Version requirement sets requirements for non-NT based operating systems, while the Windows NT Version requirement sets requirements for NTbased operating systems. The Minimum System Requirements dialog appears. 3. In Windows Version, select a version that is older than the operating system on your computer. If you select one that is newer, the installation wont run on your computer. In Message Text, enter: This installation requires Windows <version> or later. where <version> is the version you selected in the Windows Version field above. 5. Click OK.
4.
Select Dialogs That Appear to End Users

To determine the level of control the end user has over the installation, you specify which dialogs appear during installation. In this procedure, you set up the QuickFacts installation to let the end user choose which features to install. 1. 2. 3. Under the User Interface page group, select the Dialogs page. Mark the checkboxes for the Installation Type Dialog and the Select Feature Dialog. Leave the defaults for the rest of the dialogs.
44
The selected dialogs will appear during installation. The Installation Type Dialog lets the end user choose from a Typical, Complete, or Custom installation, and the Select Feature Dialog lets the end user select features in a custom installation. In the next section, you define which features are installed with each type of installation.
Configure Installation Types

You can define which features are installed when the end user selects Complete, Typical, or Custom on the Installation Type dialog. On the Installation Types page, you turn features on or off for each type of installation. 1. Under the User Interface page group, select the Installation Types page. The upper-left list box shows 3 installation types by default, Typical, Complete, and Custom, which correspond to the 3 radio buttons presented to the end user on the Installation Types dialog during installation. 2. 3. 4. In the upper-left list box, select &Typical. (The & indicates which letter will be underlined for the shortcut key.) Make sure the Default Installation Type button is disabled; if not, click it. This sets the Typical installation as the default. In the list on the right, make sure the checkboxes are marked for Core, Birds, and Cats, as shown below. Clear the Dogs checkbox. (The features might be listed in a different order in your installation.)
5. 6.
In the upper-left list box, select &Complete and, in the list box on the right, make sure the checkboxes are marked for all features. In the upper-left list box, select C&ustom and, in the list on the right, make sure the checkboxes are marked for the Core, Birds, and Cats. Make sure the Dogs checkbox is cleared, as shown below. (The features might be listed in a different order in your installation.)
7.
You have configured the installation to require a specific version of Windows and to let the end user select which features to install. In the next section, you create a standard and a demo edition of the installation.
Define Releases
In this section, you will create a standard edition and a demo edition of the QuickFacts installation. You also will customize properties for the demo release so that the product name reflects that its a demo.
45
To generate more than one installation from a single project, you create multiple releases and then configure each release. You can create releases in Wise for Windows Installer project files (.WSI) only; release options are disabled in .MSI files. When you create a release, you can specify whether the compiled installation program is an .EXE or an .MSI and whether to pre-install the Windows Installer software before running the installation. For this tutorial, you will create .MSI files and you will not preinstall Windows Installer.

Creating releases. Customizing the demo release properties. Before performing these tasks, you must have customized the installation by following the procedures in Customize the Installations Behavior on the Destination Computer on page 44.
Create Releases
In this procedure, you create 2 releases for this installation: a standard edition and a demo edition. 1. Under the Release Definition page group (you might need to scroll down to see it), select the Releases page. A release named Default already exists, because every installation must contain at least one release. 2. Double-click the Default release. The Release Details dialog appears. 3. Complete the dialog: Release Name Change this to Standard. .MSI File Name Enter: QuickFacts.msi Description Enter: QuickFacts Standard Release Installation Theme, Compression Type, Release Type Leave the defaults. Build this release during compile Make sure this is marked. 4. 5. Click OK on the Release Details dialog. Click Add at the right of the window to add the demo release. The Release Details dialog appears. 6. Complete the dialog: Release Name Enter: Demo .MSI File Enter: QuickFacts_Demo.msi
46
Description Enter: QuickFacts Demo Release Installation Theme, Compression Type, Release Type Leave the defaults. Build this release during compile Mark this checkbox. Note An Edit Media button appears at the bottom of the dialog. This button is enabled only when you first add a new release. You dont need to use it in this tutorial. 7. Click OK.
The installation now contains 2 releases. In the next section, you customize the demo release.
Customize the Demo Release Properties

When you create new releases, they retain the properties of the default release. In this installation, the default release is now called the Standard release. In this procedure, you customize the demo release so that: It includes limited features. The products name indicates that it is a demo. The products summary informs the end user that this demo release includes limited features.
To customize the demo release:

1. 2. 3. Under the Release Definition page group, select the Release Settings page. From the Current Release drop-down list, select Demo. To turn off the features that will not be included in the demo release, clear the following checkboxes under the Features icon: Cats Dogs 4. To change the ProductName property to reflect that this release is a demo edition: a. b. c. d. e. 5. Select the Properties icon. Click Add at the right of the window. The Property Settings Override dialog appears. From Name, select ProductName. In Value, enter: QuickFacts Demo Click OK.
To change the Summary settings to inform the end user that this demo release includes limited features: a. b. Select the Summary icon. Click Add. The Summary Settings Override dialog appears.
47
c. d.
From Name, select Comments. In Value, enter: This is a demo version; it contains limited features. This text appears if the end user views properties on the compiled QuickFacts_Demo.msi.
e. 6.
Click OK.
Congratulations! You have just completed an installation, without having to edit even one table. In the next section, you compile and test the installation.
Compile and Test the Installation

Now that you have completed an installation project, you need to compile it into an .MSI. Because the installation consists of 2 releases, compiling will result in 2 .MSI files, one for each release. After compiling, you can test the installation. Before performing this task, you must have created releases by following the procedures in Define Releases on page 45. Note This procedure guides you through testing the installation on your computer. If you were really distributing this installation, it would require more thorough testing on multiple operating systems. When you test the installation, it runs in test mode. The installation appears as it does to the end user, but no files are actually installed or modified, and no changes are made to the system, although the installation otherwise performs all the tasks in the installation. You can then run a full installation, which installs files and modifies the system. After you run an installation, you must uninstall before you can run the installation again. This is because Windows Installer detects when a product is installed and runs the subsequent installation in maintenance mode.
To compile and test the installation:

1. Test the standard release. Click Test at the lower right of the window. Because this installation has 2 releases, you must select which one to test. On the Select an .MSI File dialog, select QuickFacts.msi and click OK. The installation is compiled, and then a simulated installation is run for the standard release. 2. 3. Step through the dialogs of the installation until the Select Installation Type dialog appears. Click Custom and click Next. Notice that all features are visible on the Select Features dialog, though one of them has an X icon, indicating that it will not be installed. This is the result of the settings you entered on the Installation Types page. 4. Proceed by accepting the defaults on the remaining dialogs.
48
5.
When the test finishes, test the demo release. Select the demo release in the Select an MSI File dialog and repeat the preceding steps, including selecting Custom on the Select Installation Types dialog. Notice that the product name on the installation dialogs includes Demo. Also, only 2 features are visible on the Select Features dialog. This is the result of the features you set on the Release Settings page.
6. 7.
Proceed by accepting the defaults on the remaining dialogs. Now run the installation of the standard release, which installs the files. a. b. Click Run at the lower right of the window and select Run from the button menu. On the Select an .MSI File dialog, select QuickFacts.msi and click OK.
The standard release of the QuickFacts installation is run. Accept all dialog defaults and click Finish when the installation finishes. 8. Select Windows Start menu > Programs > QuickFacts. The QuickFacts application starts. The upper-left list box lists the fact files that are available for viewing. Because you installed a Typical installation, you do not see the Dogs fact files. (The Core feature, which comprises the QuickFacts application and help, is installed also.) Exit QuickFacts and double-click a .QFT file in Windows Explorer, which should launch QuickFacts. The .QFT files are in Program Files\QuickFacts\FactFiles. Note Do not run an actual installation of the demo release. The demo release cannot be installed until the standard release has been uninstalled. This completes the basic Wise for Windows Installer tutorial. Now you know how to create an installation using Installation Expert. The Advanced Tutorial describes how to add custom actions to the installation using the MSI Script view.
49
Chapter 6
Advanced Tutorial: Using MSI Script

This tutorial guides you through the basics of creating custom actions. Because this tutorial builds on the installation you created in the previous chapter, you must first complete Basic Tutorial: Creating an Installation on page 36. This tutorial takes about 30 to 45 minutes to complete. If you stop before finishing this tutorial, save the installation and resume the tutorial at a later time. This tutorial contains examples of: How to call a .DLL. How to call an .EXE. How to set a directory based on end user input. These exercises demonstrate the power and versatility that custom actions add to the installation-building process. This section also describes some of the advanced tasks you can perform using Setup Editor.
Call a .DLL With a Custom Action

In this section, you create a custom action that displays a dialog during the installation of files. The dialog shows the value of the property INSTALLDIR, which contains the default installation directory. To do this, you call a standard Windows .DLL that already exists on the destination computer. This exercise demonstrates calling a .DLL, not displaying a message dialog. There is an easier way to display a message dialoguse the Display Message action in MSI Script. Note The property INSTALLDIR stores the default installation directory. It defaults to the first directory you create in the installation. You can see it in the Default Directory field in Installation Expert > Product Details page. During installation, the end user can change the value of INSTALLDIR on the Single Feature Destination dialog.
To call a .DLL during installation:

1. In Wise for Windows Installer, open QuickFacts Installer.wsi, which you created during the basic tutorial. It may already be open if you are continuing from the basic tutorial. 2. Click MSI Script at the lower left of the Wise for Windows Installer window. MSI Script contains the sequences of actions that make up an installation. 3. Make sure Normal Installation is selected in the Installation Mode drop-down list. Normal Installation refers to a regular installation or uninstallation of the product.
50
4.
Click the Execute Immediate tab at the bottom of the Installation Sequence pane. You will add the action to the Execute Immediate sequence immediately before the installation of files begins.
5.
Locate the InstallFiles action in the Execute Immediate script: a. b. c. d. Press Ctrl+F to open the Find dialog. In the Find dialog, enter InstallFiles in the Find What field and make sure Normal Installation is selected in the In What drop-down list. Click Find Next. Click Cancel after the InstallFiles action is found.
6.
Select the REM statement above the InstallFiles action. When you add a new action, it always appears above the line that is selected in the right pane.
7.
In the Actions list, double-click Call Custom DLL from Destination. Call Custom DLL actions let you send parameters while Call DLL actions do not. The Call Custom DLL From Destination dialog appears. Note Although this tutorial guides you through calling a particular Windows .DLL function, it is not the purpose of this tutorial to teach you about .DLLs. Consult Windows developer documentation or other documentation to learn more about calling system .DLLs or the MessageBoxA API.
8.
Click the Details tab and complete the dialog: Note This tutorial does not explain all the options available on this dialog. Press F1 on the dialog for details on all options. Custom Action Name Enter: DisplayMessageBox DLL File (Windows NT, 2000, or XP.) Enter: SystemFolder\user32.dll (Windows 95, 98, or Me.) Enter: System16Folder\user32.dll The predefined directories, SystemFolder and System16Folder, hold paths to the \System32 and \System directories, respectively. All predefined directories are listed in the Directory table in Setup Editor > Tables tab. If you would actually deploy this action, youd have to construct If Statement structures that checked the operating system and then referred to the correct directory. Function Name Enter: MessageBoxA (case-sensitive), which is the name of a function within User32.dll. Parameters List In the parameters list, use the Add button to add the 4 parameters listed below. Click OK on the DLL Parameter Details dialog after entering each parameter. First parameter:
51
Parameter type: long Value Source: Constant with NULL value Because Constant with NULL value passes a value of NULL regardless of the parameter type, the Details tab displays Not applicable for the parameter type. Second parameter: Parameter type: string pointer Value Source: Property Property Name: Enter: INSTALLDIR Third parameter: Parameter type: string pointer Value Source: Constant Constant Value: Enter: The value of INSTALLDIR is: Fourth parameter: Parameter type: long Value Source: Constant Constant Value: Enter: 0 9. Leave the defaults for the Return fields and the Properties tab. The dialog should look like this:
10. Click OK on the Call Custom DLL From Destination dialog. The action is added to the sequence, immediately after the MoveFiles action. The next steps demonstrate how to enclose the new action in an If Statement, which sets a condition on the actionthe action runs only if the condition is true. 11. Select the Call Custom DLL From Destination action that you just created, and then in the Actions list, double-click If Statement.
52
The If Settings dialog appears. 12. In If Condition, enter NOT Installed (case sensitive) and click OK. The Windows Installer property named Installed is true if the product is already installed, so this action will run only on the initial installation of the product, not on subsequent maintenance installations. See Installed Property in the Windows Installer SDK Help. 13. Select the line below the Call Custom DLL From Destination action and double-click End Statement in the Actions list. This encloses the custom action in an If block, which is located between MoveFiles and InstallFiles and should look like the image below. If not, double-click the actions to edit their settings or use the Move Up and Move Down commands on the rightclick menu to rearrange the lines.
To test the custom action:

1. 2. 3. Save the installation. Compile the installation by clicking Compile at the lower right of the main window. To run the installation, click the Run button, select Run from the button menu, and when prompted, select QuickFacts.msi. If QuickFacts is already installed, the Application Maintenance dialog appears. Mark Remove and click Next to uninstall it. Then run the QuickFacts.msi again. Note Avoid uninstalling by selecting one of the other options from the Run button, which either uninstalls and then reinstalls, or forces a reinstall over an installed product. 4. In the installation wizard, click Next until the installation of files begins. During installation of files, a small dialog appears when Windows Installer calls the function MessageBoxA from user32.dll.
5.
Click OK to close the dialog and then click Finish at the end of the installation. If the dialog does not appear as expected, verify that the parameters and function name in the custom action match the instructions in this tutorial. Also verify that the custom action is in the correct position in the sequence.
53
Set a Directory With a Custom Action

In this section, you create a custom action that changes the location of the installation based on end user interaction with the installation wizard. To do this, you: Create a checkbox on the Single Feature Destination dialog. Create a custom action that redefines the installation directory so that it is located under the Common Files directory. During installation, the end user can mark or clear the checkbox, thereby triggering or skipping the custom action.
To create a checkbox on the Single Feature Destination dialog:

1. 2. Click Setup Editor at the lower left of the Wise for Windows Installer window. In the right pane, click the Dialogs tab, and then find and select the dialog named Single Feature Destination, which appears under Install Dialogs. The dialog, which is labeled Destination Folder, appears in the upper-right pane.
3.
In the blank area under the Destination Folder group box, right-click and select Add > Checkbox. The Properties for Checkbox dialog appears, where you set a property and control text associated with the checkbox.
4.
In Control Text, enter: Put installation under the Common Files folder This is the text label for the checkbox.
5.
Click the New button to the right of the Property drop-down list. The Property Details dialog appears, where you create a new property to hold the value of the checkbox.
6.
Complete the dialog:
54
a. b. c. d. e.
In Name, enter COMMONDIR (all uppercase). Leave the Value field blank. The checkbox value must evaluate to blank (nothing) initially so that the checkbox is not marked when end users first see it. Leave the defaults in the remaining fields. Click OK.
Note Technically, leaving a property blank is not allowed according to Windows Installer guidelines, but in this tutorial, you leave it blank so that the checkbox is initially unmarked. Because the property value is blank, the property does not appear under the Properties icon in Setup Editor > Product tab. 7. Click OK on the Properties for Checkbox dialog. The checkbox appears on the Destination Folder dialog. 8. If necessary, drag the checkbox so it is aligned with other controls on the dialog.
In the next procedure, you create a custom action that tests the value of the COMMONDIR property during installation. If COMMONDIR is true (which means that the checkbox is marked), the custom action resets the value of the installation directory (INSTALLDIR) so that it is placed in the Common Files directory.
To add a custom action that defines INSTALLDIR based on user input:

1. 2. 3. Select MSI Script. Make sure Normal Installation is selected in the Installation Mode drop-down list. Click the User Interface tab at the bottom of the Installation Sequence pane. For this tutorial, you add the action to the User Interface sequence immediately after the Welcome_Dialog If block. The Welcome_Dialog action contains all the wizard dialogs the end user sees during installation. The User Interface sequence gathers end user input and sets installation properties. 4. Scroll to near the end of the script and select the If Installed AND (RESUME OR Preselected) AND NOT PATCH then statement. You will place a new If block above this line. In the Actions list, double-click Set Directory. The Set Directory dialog appears. 6. Click the Details tab and complete the dialog: Custom Action Name Enter: ChangeDirectory Directory Browse to the QuickFacts directory, which is the installation directory represented by the INSTALLDIR property. Click OK. INSTALLDIR appears in the Directory field. If the end user marks the Put installation under the Common Files folder checkbox during installation, this is the directory whose location is redefined.
5.
55
Directory Value Enter (case-sensitive): [CommonFilesFolder]QuickFacts This will be the new location of the installation directory if the end user marks the checkbox during installation. CommonFilesFolder is a directory property that represents the Common Files directory on the destination computer. 7. Leave the defaults on the Properties tab. The dialog should look like this:
8.
Click OK on the Set Directory dialog. The action is added to the sequence, immediately after the Welcome_Dialog If block. In the next steps, you enclose this action in an If Statement, which sets a condition on the actionthe action runs only if the condition is true.
9.
Make sure the Set Directory custom action you just created is selected. In the Actions list, double click If Statement. The If Settings dialog appears.
10. In If Condition, specify 2 conditions joined by AND. Enter the following (casesensitive) and click OK: COMMONDIR AND NOT Installed The first condition checks the COMMONDIR property you attached to the Put installation under the Common Files folder checkbox, which is true if the end user marks it during installation. The second condition checks a built-in Windows Installer property, named Installed, which is true only if this is the initial installation of the product, not a reinstall or maintenance installation. 11. Place an End Statement below the Set Directory custom action. The If Statement, custom action, and End Statement should look like the image below. If not, double-click the actions to edit their settings or use rearrange the lines. to
56

1. 2. 3. Save the installation. Compile the installation by clicking Compile at the lower right of the main window. To run the installation, click the Run button, select Run from the button menu, and when prompted, select QuickFacts.msi. If QuickFacts is already installed, the Application Maintenance dialog appears. Mark Remove and click Next to uninstall it. Then run the QuickFacts.msi again. Note Avoid uninstalling by selecting one of the other options from the Run button, which either uninstalls and then reinstalls, or forces a reinstall over an installed product. 4. In the installation wizard, click Next on all the dialogs, leaving the Put installation under the Common Files folder checkbox cleared. Because of the custom action you added earlier in this tutorial, a dialog displays the value of INSTALLDIR during installation. After installation, notice that the QuickFacts directory is in the Program Files directory. 5. Now uninstall QuickFacts and run the installation again, this time marking the Put installation under the Common Files folder checkbox. When this installation is finished, the QuickFacts directory should appear in your Common Files directory. Note If you are running Windows 95 or Windows 98, and this custom action does not work, go to the Merge Modules page and add the merge module CondFix to the installation. This merge module fixes a Windows Installer limitation with setting properties during the UI Sequence. See the description of CondFix in the Wise for Windows Installer help.
Call an .EXE With a Custom Action

In this section, you create a custom action that calls an .EXE and passes parameters to it. This action calls Notepad.exe and passes the name of the QuickFacts readme file to it, causing the readme file to be displayed during installation.
To create a custom action that opens a file in the installation:

1. 2. Select MSI Script. Make sure Normal Installation is selected in Installation Mode.
57
3.
Click the Execute Deferred tab at the bottom of the Installation Sequence pane. For this tutorial, you add the action to the Execute Deferred sequence immediately after the InstallFiles action. This action must run in deferred mode because it relies on an installed file (readme.txt), which is not present on the destination computer until after the InstallFiles action runs in the Execute Deferred sequence.
4.
Locate the InstallFiles action in the Execute Deferred script: a. b. c. d. Press Ctrl+F to open the Find dialog. In the Find dialog, enter InstallFiles in the Find What field and make sure Normal Installation is selected in the In What drop-down list. Click Find Next. Click Cancel after the InstallFiles action is found.
5. 6.
Select the REM statement below the InstallFiles action. In the Actions list, double-click Execute Program From Destination. The Execute Program From Destination dialog appears.
7.
Click the Details tab and complete the dialog: Note This tutorial does not explain all the options available on this dialog. Press F1 on the dialog for details on all options. Custom Action Name Enter: OpenReadMe Working Directory Enter: INSTALLDIR This sets the current working directory of the .EXE when it runs on the destination computer. In this case, Notepad.exe looks in the installation directory for the readme file you specify below. EXE and Command Line Enter: notepad.exe readme.txt Note Because Notepad is in the PATH variable, you do not have to specify its full path. If you were calling an .EXE that is not in the PATH variable, you would have to specify the full path here, using bracketed property names to form the pathname. Also, you dont have to specify the full path to readme.txt because in the previous field you set Notepads current working directory to the QuickFacts directory, where readme.txt resides. The dialog should look like this:
58
8. 9.
Click the Properties tab. In Processing, select Asynch, No wait, which makes the installation continue after opening Notepad.
10. Click OK on the Execute Program From Destination dialog. The action is added to the sequence immediately after the InstallFiles statement. In the next steps, you enclose the action in an If Statement, which sets a condition on the actionthe action runs only if the condition is true. 11. Above the Execute Program From Destination action, add an If Statement action. In If Condition, enter: NOT Installed. 12. Click OK. 13. Below the Execute Program From Destination action, add an End Statement. The If Statement, custom action, and End Statement, which are located between InstallFiles and PatchFiles, should look like the image below. If not, double-click the actions to edit their settings or use to rearrange the lines.

1. 2. 3. Save the installation. Compile the installation by clicking Compile at the lower right of the main window. To run the installation, click the Run button, select Uninstall ---> Install from the button menu, and when prompted, select QuickFacts.msi.
59
4.
In the installation wizard, click Next until the installation of files begins. Because of the custom action you added earlier in this tutorial, a dialog displays the value of INSTALLDIR during installation. After the installation of files, Notepad should appear and display the readme.txt file. If this does not work, check the order of the custom action. It must occur after the InstallFiles action, or it will not work. Also make sure it is in the Execute Deferred sequence and that all fields are entered correctly.
This completes the tutorial. The next section describes some of the advanced tasks you can perform in Setup Editor.
Performing Advanced Tasks

As you learned from the Basic and Advanced Tutorials, you can easily build complete installations without using Setup Editor. If you are developing complex installations, however, you might need to perform fine-tuning or advanced tasks in Setup Editor. To access Setup Editor, click Setup Editor at the lower left of the window. In Setup Editor, you can: Edit tables of the Windows Installer database (recommended for advanced Windows Installer developers only). Edit installation dialogs by adding and editing text and controls. Select dialogs to appear during maintenance installations (repair and uninstall). Create properties for use in custom installation logic. Create and edit components manually and assign them to features. Build complex conditions that must be met for installation to occur. For instructions on the tasks listed above, see Wise for Windows Installer help.
60
Chapter 7
Tutorial: Visual Studio Integrated Editor

If you use Visual Studio integrated editor, first do the Basic tutorial using the Wise editor. Then do this tutorial using Visual Studio integrated editor. This tutorial includes only procedures that have content that is specific to the Visual Studio integrated editor. This tutorial takes about 30 minutes to complete. If you must stop before finishing this tutorial, save the installation and resume the tutorial at a later time. In this tutorial, you will use Installation Expert to: Open the C# QuickFacts solution and create an installation project. Open the installation project and set options. Enter product details and general information. Add files to the installation.
Open the C# QuickFacts Solution and Create an Installation Project

1. 2. 3. 4. Launch Microsoft Visual Studio .NET. Select File menu > Open > Project. Navigate to the Tutorial\Integrated Tutorial\QuickFacts subdirectory of the Wise for Windows Installer application directory. Select QuickFacts.sln and click Open. Note If you are using Visual Studio .NET 2003, a message appears asking if you want to convert this solution. Click Yes. If a message appears about some properties not being read, click OK. QuickFacts is a solution, written in C#, that consists of 3 projects: FactFinder, which compiles to FactFinder.dll. QuickFacts, which compiles to QuickFacts.exe. TextViewer, which compiles to TextViewer.dll. QuickFacts is dependent on FactFinder, and FactFinder is dependent on TextViewer. 5. 6. Select Build menu > Build Solution to compile all projects. Select File menu > New > Project. The New Project dialog appears. 7. On the New Project dialog: a. b. In Project Types, select Wise Setup and Deployment Projects. In Templates:
61
(Standard Edition.) Select Windows Application. (Professional and Enterprise Editions.) Select Setup Wizard. c. d. e. f. In Name, enter QuickFacts Installer. Before setting the Location, mark the Add to Solution option. In Location, specify the Program Files\Wise for Windows Installer\Tutorial\Integrated Tutorial\QuickFacts directory. Click OK.
(Standard Edition.) The Wise Setup Wizard steps below are skipped. Go to the end of this procedure. (Professional and Enterprise Editions.) The Wise Setup Wizard appears with pages for Overview, Project Type, Projects, and Main Project. 8. Select the Overview page. It contains a summary of the settings for the installation project. It indicates that the primary outputs for each project (TextViewer.dll, FactFinder.dll, and QuickFacts.exe) are added to the installation project. 9. Select the Project Type page. This page is used to specify the type of Windows Installer project to create. For this tutorial, leave Windows Application marked. 10. Select the Projects page. The default settings should be correct. Select the projects to include in this package The solutions projects are selected. Scan Method With Always Scan Solution selected, if the primary outputs for the 3 projects change, the files in the installation will change accordingly. Bind installed files to the solution build configuration With this marked, if you change your build configuration from Release to Debug or vice versa, the installation project will draw its files from the corresponding directories. 11. Select the Main Project page. The default settings should be correct. Main Project QuickFacts should be selected. Automatically Update Product Information With this marked, the version number and other summary information in the installation is updated whenever the main target file changes. The information is updated each time you build your solution. Create Shortcut With this marked, a shortcut is created for the installation project. Target Platform This is a 32-bit installation. 12. Click Finish. A new project named QuickFacts Installer is added to the other projects in Solution Explorer. (If Solution Explorer is not visible, select View menu > Solution Explorer.) FactFinder.dll, QuickFacts.exe, and TextViewer.dl are in the projects Source Files
62
folder. They were added to the installation project because they are primary output files from the existing C# projects.
Open the Installation Project and Set Options

You use the Wise Options dialog to customize the behavior of Wise for Windows Installer for all installations you create. Windows Installer projects are comprised of features, and normally, you view folders and registry keys per feature. In this procedure, you open the installation project that you created and set options that let you view folders and registry keys for all features simultaneously, making it easier to see the installation as a whole. 1. In Solution Explorer, double-click QuickFacts Installer.wsi. Make sure you doubleclick on the .WSI file, shown below, not the project name:
The Visual Studio integrated editor opens and displays QuickFacts Installer.wsi. 2. Select Tools menu > Options. The Options dialog appears. 3. 4. In the left pane, click Wise Options to expand the list and then select Installation Expert. In Installation Expert Options, mark the following. If you marked these in the Basic tutorial, they will be marked already. View directories for all features on Files page This lets you see all directories in Installation Expert > Files page, regardless of what feature each directory was created for. View registry keys for all features on Registry page This lets you see a composite view of all registry keys in Installation Expert > Registry page, regardless of what feature the registry key was created for. Note To display context-sensitive help, click Wise Help on the Options dialog. 5. Click OK.
Enter Product Details and General Information

To enter information about the installation, you use pages in the Project Definition page group in Installation Expert. 1. 2. 3. If necessary, maximize screen space by closing other windows, such as Solution Explorer, Properties, Class View, Output, and Dynamic Help. Click Installation Expert at the lower left of the Wise for Visual Studio .NET window. Under the Project Definition page group on the left, click Product Details. The Product Details page appears. It contains meta data that is used in the installation dialogs to identify the product to the user who is installing it. The Product Name, Manufacturer, Version, and Default Directory fields are populated with information from the main project.
63
4. 5.
(Professional and Enterprise Editions only.) In the Application Type field, select .NET Application in the Value column. Leave the defaults in the remaining fields. Select the General Information page by clicking its name. On the General Information page, you set the information that appears when the end user right-clicks the installation file in Windows Explorer and selects Properties.
6.
Complete the General Information page: Title Enter: QuickFacts Author Enter your name.
7.
Select the Add/Remove Programs page. On the Add/Remove Programs page, you enter information to support the capabilities of the enhanced Add/Remove Programs control panel that was introduced with Windows 2000.
8.
Complete the Add/Remove Programs page: Display in Add/Remove Programs list Make sure this is marked. Online Info URL Enter: No support provided.
9.
Save the installation by selecting File menu > Save QuickFacts Installer.wsi.
Now that youve entered basic information about the installation, you can define the features that provide structure to the installation. To do this, see Create and Organize Features on page 39. After you define features, you can add files to the installation.
Add Files to the Installation

On the Files page, you specify the directories and files that will be installed on the destination computer. You specify files per feature; the files that you add are only installed on the destination computer if the feature is installed. Because this installation has multiple features, be sure to specify the feature for which you are adding files. You do this by selecting it from the Current Feature drop-down list. 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. Therefore, this installation already contains files that are primary outputs of the 3 C# projects. You only need to add files that are not within the solution. Before performing this procedure, you must add features as described in Create and Organize Features on page 39.
To add files to the Core feature:

1. Under the Feature Details page group, select the Files page. Note To display context-sensitive help, press F1. 2. From the Current Feature drop-down list, select Core.
64
3.
In the lower-left list box, find and select Program Files\QuickFacts. It contains 3 files (FactFinder.dll, QuickFacts.exe, and TextViewer.dll) that are primary output files of the 3 C# projects.
4.
In the upper-left list box, navigate to the Tutorial\Integrated Tutorial\Content Files subdirectory of the Wise for Windows Installer application directory. The files in the Content Files directory appear in the upper-right list box.
5.
Make sure the QuickFacts directory is still selected in the lower-left list box. In the upper-right list box, select License.txt and ReadMe.txt and click Add File. The 2 files are added to the QuickFacts directory in the installation.
6. 7. 8.
In the upper-left list box, expand the Content Files directory and select the Help subdirectory. Make sure the QuickFacts directory is still selected in the lower-left list box, and click Add Contents. On the Add Contents dialog, leave the defaults and click OK. The Help directory and its contents are added to the installation.
9.
10. If the Copy Source Files dialog appears, click Cancel. This has to do with Source Code Control, which is not used in this tutorial. In the Current Feature drop-down list, the number (7) should appear next to the Core feature name. This indicates that the Core feature contains 7 files. This completes the file additions for the Core feature. To add files to the remaining features, see To add files to the remaining features: on page 41. The rest of the procedures in the Basic tutorial are the same for both editors except for the following differences for the Visual Studio integrated editor: You dont need to add a shortcut on the Shortcuts page, because it is added automatically. However, you need to change its destination directory to Windows\Profiles\Start Menu\Programs. To compile the installation, select Build menu > Build QuickFacts Installer. To test the installation, select Project menu > Start in Test Mode. To run the installation, right-click the QuickFacts Installer project icon in Solution Explorer and select Set as Startup Project. Then select Debug menu > Start Without Debugging. For other differences between the Wise editor and the Visual Studio integrated editor, see the Wise for Windows Installer Help.
65
Index
Symbols
.NET Framework requirements 16 requirements 17 evaluation converting to production 24 Enterprise Edition 17 installation 15 tutorial 36 Wise Repository Manager 27
A
Access 16 Altiris consulting 7 getting updates 8 training 7 authentication best practices 18 setting 34
F
file share name 34
R
readme See release notes reference manual accessing online 6 registration, product 24 release notes 6
G
Getting Started Guide 6
H
help about 5 using 6 Windows Installer SDK 6
B
best practices authentication 18 configuration 9
repository See Wise Software Repository requirements Wise Repository Manager 27
I
installation Language Pack 23 options 19 upgrade 19 integrated editor, tutorial 61
S
sales contact 8 sample applications 35 serial number 17 server installation about 19 default repository 33 share point directory 33 settings, database 31 share point sharing 18 where to locate 17 share point directory on separate server 13 share name 34 specifying for client 23 specifying for server 33 unsupported configuration 13 show upgrade log 31 Software Manager database 17, 27 creating 31 multiples 12 sample applications 35 SQL Server 16 start Wise Repository Manager 27 starting Wise for Windows Installer 24 subscriptions 28 support 7 newsgroups 7 online support 7 system requirements .NET Framework 16 database 16 Wise for Windows Installer 15
C
checking for updates 8 client installation share point directory 23 configuration best practices 9 dedicated SQL server 10 multiple repositories 12 single server 11 configure repository 29 consulting 7 create new users 35 creation options (database) 35
L
Language Pack, installing 23 launch Wise Repository Manager 27 launching Wise for Windows Installer 24 logon database administrator 34 database service 34
D
database creation options 35 identification 34 registering 31 requirements 16 settings, changing 31 upgrading 30 users, creating 35 where to install 9 database administrator logon 34 database service logon 34 database tree 28 database, Software Manager See Software Manager database documentation 5
M
manual accessing online 6 Microsoft Access 16 Microsoft Data Engine 16 Microsoft SQL Server 16 MSDE 16 MSI Script, tutorial 50
N
new features Refer to Release Notes new repository 32 newsgroups 7
P
prerequisites .NET Framework 16 database 16
E
Enterprise Edition
66
system requirements, Wise product Refer to Getting Started Guide
T
technical support 7 newsgroups 7 online support 7 training 7 tutorial advanced 50 basic 36 integrated editor 61 prerequisites 36 Refer to Getting Started Guide
U
update, checking for 8 upgrade database 30 installing 19 log 31 Wise Software Repository 30 user account, Wise service changing 35 setting 22
V
Visual Studio integrated editor tutorial 61
W
Windows Installer developer documentation 6 help 6 Windows Installer SDK Help 6 Wise Package Studio configuration 9 Wise Repository Manager interface 28 requirements 27 starting 27 Wise service account changing 35 setting 22 Wise Services database about 27 Wise Software Repository 26 active 27 client default 33 configuring 29 creating 32 multiples 12, 27 new 32 opening 33 server default 33 upgrading 30
67

Getting Started Guide

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Getting Started Guide

Transféré par

Droits d'auteur :

Formats disponibles

Wise for Windows Installer Getting Started Guide

Wise for Windows Installer Getting Started Guide

Chapter 2: Configuration Best Practices for the Enterprise Edition . . . . . . . . . . . . . . . . . 9

Chapter 3: Installing Wise for Windows Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 4: Managing the Wise Software Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 5: Basic Tutorial: Creating an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Wise for Windows Installer Getting Started Guide

Chapter 6: Advanced Tutorial: Using MSI Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 7: Tutorial: Visual Studio Integrated Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Wise for Windows Installer Getting Started Guide

Wise for Windows Installer Getting Started Guide