Windows Installer Editor Reference
244
Advanced Installations
a. Use a computer that has the .NET Framework installed and has the assemblies.
This typically is a development computer.
b. For each assembly, run the ildasm tool from the Visual Studio .NET command
prompt. When you run ildasm, you select an assembly and the program displays
the assembly’s attributes. Write down the assembly’s culture, name,
publicKeyToken, and version, as well as any dependencies.
c.
On the Files or Web Files page, add the dependency assemblies to the same
directory as the assembly that has the dependencies. Repeat for each assembly.
d. In the lower right pane of the Files or Web Files page, double-click an assembly
to display the File Details dialog box. Click the Assembly tab. Click Add to add
the Name and Value of the assembly’s culture, name, publicKeyToken, and
version. Repeat for each assembly.
See
Editing Assembly Settings for Files
on page 127.
5. If the installation contains both .NET and Win32 components, register the .NET
components for COM interop.
a. Use a computer that has the .NET Framework installed and has the assemblies.
This typically is a development computer.
b. For each .NET assembly, run the Assembly Registration tool (regasm) from the
Visual Studio .NET command prompt. Run regasm with the argument /regfile
and specify a file name.
Example: regasm AssemblyFileName /regfile:RegFileName.reg.
This command generates a .REG file containing the registry entries you need to
allow the .NET assembly to be called as a COM component. Search for
“Assembly Registration Tool (Regasm.exe)” in the MSDN Library
(
msdn.microsoft.com/library/
).
c.
On the Registry page, import the .REG file you created for each assembly.
See
Adding Registry Keys
on page 141.
6. If the destination computer does not contain the .NET Framework, add support for
the .NET Framework to the installation. On the Prerequisites page, select the
desired release and then select the runtime from .NET Framework Runtime
Version.
The Windows Vista and later operating systems already include the .NET
Framework.
See
Adding Prerequisites to a Release
on page 198.
7. Finish building the installation as usual, then compile and distribute it.
See also:
About Microsoft .NET Technology
on page 497
Requirements for Creating a .NET Installation
on page 501
Frequently Asked Questions About Microsoft Windows Installer
on page 495
Creating a .NET Installation When You Have the .NET Framework
on page 242
