Using A Wise Package Studio Repository - Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Using a Wise Package Studio Repository

Windows Installer Editor Reference
2. Click anywhere outside the box that contains the new task.
The task is added to the Task List and appears in the Description column. User-
defined tasks do not use the Tables column.
See also:
Using the Task List on page 26
Requires a repository connection.
You can connect to a Wise Software Repository that has been configured for an
installation of Wise Package Studio 8.0 or later. To do so, use the Repository Client
Manager.
See Connecting to a Wise Software Repository
Use information in the Wise Software Repository to develop consistent, accurate, and
high quality applications and installations:
Improve Applications During Development and Testing
Use the Wise Software Repository to mirror your production environment. The Wise
Software Repository™ is a collection of resources, and information about those
resources, for internally developed and third-party applications.
To import and manage information in the Wise Software Repository, use Software
Manager.
See About Importing Packages in the Software Manager Help.
Understand how the application will behave in the production environment so you
can identify and resolve potential conflicts during the application's development.
Check each file and registry key you add to an installation for possible conflicts
with those in other applications. Example: A developer who adds or updates a
.DLL to an installation can instantly view a list of other applications that use that
.DLL and the versions used. The developer can use this information to ensure
that the new application uses the correct version of the .DLL and therefore will
not break existing applications.
See Viewing Shared File Resources
Resources on page 170.
View the file and registry resources that are shared among applications in the
target environment so you can identify potential problems.
See Generating Shared Resource Reports
Collaborate on and Standardize Installation Development
Share installation resources to enforce organizational standards and maintain a
consistent look and feel across your installations. Example: Develop a set of
common component rules to ensure that every installation will be organized the
same way.
You can share the following resources:
Component rules
on page 65.
on page 152 and Viewing Shared Registry
on page 31.
Introduction
29