User Guide
543
About Microsoft .NET Technology
I thought .NET meant I could use XCOPY to install applications without
registration. Why do I need to build a Windows Installer installation?
For a .NET application that uses only managed code and private assemblies, the
installation process can be as simple as copying files to the destination computer. Most
developers, however, still need to create a compressed, single-file installation that is
easy to deploy and that provides a friendly interface to the end user.
.NET applications that use shared assemblies, or that have a mix of managed and
unmanaged code, cannot be installed via XCOPY. You should use the Windows Installer
service for installations that do any of the following:
! Install COM files
! Install assemblies to the Global Assembly Cache
! Require user information during the installation
! Require security
! Create a shortcut
! Require elevated privileges to install on a locked-down computer
By creating a Windows Installer installation for your .NET applications, you can take
advantage of the services Windows Installer provides: installation, repair, and removal
of assemblies; roll back; install-on-demand; patching; and advertisement.
How does Wise for Windows Installer support .NET installations?
Wise for Windows Installer lets you install .NET assemblies into the Global Assembly
Cache, or as side-by-side or private assemblies. It also lets you create mixed
installations by registering .NET assemblies with COM.
If the .NET Framework is installed on your computer, Wise for Windows Installer can
automate the process as follows:
! Find all files in multifile assemblies and add them to the installation.
! Scan for assembly dependencies and add them to the installation.
! Determine attributes for registering the assembly files and add them to the
MsiAssemblyName table.
! Add registry keys for COM interop.
Requirements for Creating a .NET Installation
The ability to create .NET installations is supported only by Windows Installer 2.0 or
later. When you create a .NET installation, you should have the .NET Framework
installed on your computer. If the .NET Framework is installed on your company’s
development computers, but not on the computer used to build installations, it is
possible to create a .NET installation. However, you must enter certain information
manually. See Creating a .NET Installation Without the .NET Framework on page 215.
You can build .NET installations without having Windows XP on your computer. However,
in order to take advantage of side-by-side assembly sharing, the destination computer
must have Windows XP installed. To use the Global Assembly Cache, the destination
computer must have the .NET Framework installed.
Before you begin to create an installation for your .NET application, do the following:
1. Gather all your assemblies, both Win32 and .NET, and their manifests into a
common location.
2. Determine the directories in which the assemblies are to be installed.