Table of Contents
Advertisement
Windows Installer Editor Reference
For details, search for "Windows XP visual style" in the MSDN Library
(msdn.microsoft.com).
9.
Click OK, then click OK on the File Details dialog box.
The manifest file is created in XML format and added to the installation with the same
name as the dependent file plus ".manifest". (Example: The manifest for My.exe would
be named My.exe.manifest.) The manifest is also added to your computer with the
extension .XML. (Example: If you add C:\Program Files\My.exe and make it a Win32
assembly, the file C:\Program Files\My.exe.xml is created.)
See also:
Editing File Details
on page 145
Editing Assembly Settings for Files
Viewing Shared File Resources
Requires a repository connection.
The Shared Resources tab on the File Details dialog box displays all packages in the
Software Manager database that use a specific file, even if they install the file to a
different location. This lets you:
Determine the correct version of the file to use in your application by checking
whether the file is used by packages that have already been deployed.
Resolve potential file conflicts during the development cycle. When the file in the
current installation conflicts with a file in the Software Manager database, you can
replace the current file with the correct version from the repository.
You also can view shared file resources in a report format.
See
Generating Shared Resource Reports
To view shared file resources
1.
Do one of the following:
In Installation Expert: On the Files or Web Files page, double-click a file.
In the Visual Studio integrated editor, you also can use the Visual Studio
Solution page.
In Setup Editor: On the Components or Features tab, double-click a file.
The File Details dialog box appears.
2.
Click the Shared Resources tab.
In the Visual Studio integrated editor, "Output from current solution" in the
Application column indicates a file that is in the current Visual Studio solution.
A white exclamation point to the left of the package indicates that the current file is
already in the Software Manager database and it does not conflict with the file used
by that package.
A red exclamation point to the left of the package indicates that the current file
conflicts with the file used by that package. Examples: The files have a different
version, date/time, or size; the files are installed to the same directory, but
component GUIDs do not match.
on page 149
on page 31.
Assembling an Installation
152
Advertisement
Table of Contents
Troubleshooting
