Windows Installer Editor Reference
348
Chapter 12
Working With Source Paths
This chapter includes the following topics:
z
Using Source Control
on page 348
z
About Path Variables
on page 356
z
Source Paths in an Installation
on page 359
About source paths
You might find that you need to work with source paths during installation development.
Project files (.WSI) reference files you add to the installation by their source path. Each
time you compile, the files are copied from the source path to the .MSI.
If you have a repository connection, you can distribute an installation to the share point
directory so that it can be imported into the Software Manager database. When you
distribute to the share point, all the installation’s source files are copied to the share
point and the source paths for those files are updated in the installation.
See
Copying an Installation to the Share Point Directory
on page 313.
Using Source Control
¾
Not available in the Visual Studio integrated editor.
Visual Studio contains built-in source control functionality.
Source code control is the control, tracking, and recording of all changes made to a set
of source code files. Various commercial and open-source software applications, such as
Microsoft Visual SourceSafe, act as source code control systems (SCCS). All SCCS
applications have similar functionality: tracking who is working on what file; allowing for
retrieval of previous versions, backing out of changes, adding and removing files from
the SCCS; and recording the history of files. They might also provide functionality for
viewing the differences between versions of files.
Windows Installer Editor integrates with leading SCCS applications to let you perform
source control tasks on an installation. Windows Installer Editor determines the SCCS
that you are using and calls APIs that interact with it. The API functions display dialog
boxes and functionality directly from your SCCS. On the Source Control tab in Wise
Options, you enable source code control and set the global level of interaction between
your SCCS and Windows Installer Editor.
See
Setting Source Control Options
on page 51.
To use source control, you must:
z
Have an SCCS installed on your computer, have a valid account, and you might need
permissions to create new directories and add files. Because Windows Installer
Editor works though your existing user account, the permissions you experience in
Windows Installer Editor are the same as those you already have set in your SCCS.