Windows Installer Editor Reference
243
Advanced Installations
Windows Installer Editor finds all multifile assemblies and adds them automatically.
Depending on the Scan Dependencies option in Wise Options, dependency
assemblies might be added automatically, or you might be prompted to add them. If
the option to Never scan dependencies is selected, you must add the
dependencies.
4. 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.
5. 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 Without the .NET Framework
on page 243
Setting a Requirement on the System Requirements Page
on page 165 (for information
on setting the required .NET Framework version)
Creating a .NET Installation Without the .NET
Framework
¾
Windows Installer 2.0 or later only.
You can build an installation for a .NET application even if you do not have the .NET
Framework installed on your computer. Perhaps your company’s development computers
have the .NET Framework, but the computer you use to build installations does not. If
you do not have the .NET Framework, you must do manually what the .NET Framework
normally does automatically.
To create a .NET installation without the .NET Framework
1. Select Installation Expert > Product Details page.
2. In Application Type, select either .NET Application or Mixed (.NET and
Win32).
This designates the installation as .NET and determines how Windows Installer
Editor handles COM interop registry entries.
See
Product Details Page
on page 83.
3. Add assemblies to the installation, using the Files or Web Files page.
Be sure to add all files in multifile assemblies.
See
Adding .NET Assemblies to the Installation
on page 115.
4. Add attributes and dependencies for each assembly.