Table of Contents
Advertisement
Windows Installer Editor Reference
Manifest
.NET and Win32 assemblies require a manifest. Select the file that contains the
manifest for this assembly. For .NET assemblies, this often is the same as the
file you are editing, because most manifests are embedded in the assembly file
or in one of the files in a multifile assembly. For Win32 files, the manifest is
often an external file with the same name plus ".manifest". (Example: The
manifest for My.exe would be named My.exe.manifest.)
See
Creating a Win32 Assembly
Assembly Attributes
This displays the assembly's culture, name, publicKeyToken, and version
attributes.
If this information has not been pre-filled, click Add to enter it. Enter the Name
and Value for each of the assembly's attributes.
For information on obtaining assembly attributes, see
Installation Without the .NET Framework
Show reference in Visual Studio .NET
Mark this to add a registry key that displays this assembly as a reference in
Visual Studio on the destination computer. (Visual Studio 2002 or later only.)
This lets you pull the assembly into a Visual Studio project without having to
browse for it.
Execute Install method on this assembly
A .NET assembly can contain an install object that performs additional
installation functions unique to the assembly. Mark this to execute this
assembly's install object after the file is installed.
Generate native-code version during installation
Mark this to run the Native Image Generator (ngen.exe) on the assembly after
it is installed. The Native Image Generator precompiles portions of the assembly
and caches it on the target computer so assemblies load and execute faster. For
details, search for "Native Image Generator" in the MSDN Library
(msdn.microsoft.com/library/).
4.
Click OK.
See also:
Editing File Details
on page 145
Creating a Win32 Assembly
Your can use Win32 assemblies to isolate applications on destination computers running
under Windows XP or later. Isolating an application .EXE means its dependent, shared
.DLL and .OCX files are placed in the application directory or in the WinSxS directory
rather than in a non-side-by-side location. This ensures that your application always
uses the version of .DLL or .OCX with which it was installed. It prevents overwriting of
previous versions of the .DLL or .OCX and ensures that other applications do not
overwrite your version of shared files.
You isolate a Win32 assembly by means of a manifest file, which describes the assembly
and any resources it depends on. Options for adding a Win32 assembly and its manifest
to an installation are:
Assembling an Installation
on page 150.
Creating a .NET
on page 265.
150
Advertisement
Table of Contents
Troubleshooting
