C # Study Notes (20): Windows application installation and deployment concepts

Planned Security Handover content:

1. What files are required by the application: executable files and component assembly. You do not need to identify the dependencies between these items because these dependencies are automatically included. You may need other files. For example, document files, readme.txt, license files, document templates, images, and configuration files. You must be aware of all required files.

2. What Directory should I use: the application file should be installed in program files/Application name. The naming of the Program Files directory varies with different language variants of the operating system. The administrator can also select different paths for the application. You do not need to know the location of this directory because API function calls can obtain this directory. With this installer, we can use a specific pre-defined folder to place files in the Program Files directory.

Tip: The Directory should not be hard-coded in any case. With the international version, these directories can be named differently. Even if the application supports the English version of Windows (this is not actually the case), system administrator can move these directories to different drives.

3. How to access the application: In the Start menu, we can set shortcuts for executable files and place icons on the desktop. If you want to place icons on the desktop, you should first consider whether the user is happy. For Windows XP, the principle is to make the desktop as clean as possible.

4. What is distributed media? Do we want to place the software version on CD, floppy disk, or network sharing?

5. What are the requirements for users: the user will accept the license information, display the README file, and ask about the installation path? Does the installation require some options?

 

Create a project:

 

Project properties:

1. Packaging: MSI is the database to start and install. Right-click the installation project and choose properties. The following dialog box is displayed.

In the form of loose uncompressed files: all programs and data files can be stored as they are. Files are not compressed.

In the Installation File: All files are merged and compressed into the MSI file. This option can be overwritten by a single component in a software package. If you place all the files in a single MSI file, you must note that the installation program is suitable for the desired tool, such as CD or floppy disk. If too much content is installed and exceeds the capacity of a single floppy disk, try to change the compression rate. Therefore, select the optimized size optimized for size option in the compressed compression list box. If the capacity is still not suitable, you can select the next package option.

In compressed files: archive files are used. In this method, the MSI file is used to load and install the cab file. You can use the cab file to set the file size so that the file can be installed on a CD or a floppy disk (for the installation of a floppy disk, you can set the installation capacity of KB)

2. bootstrapper wizard

That is, the "Bootstrap program" in the figure above ". Windows Installer version 1.5 is required for the installation package created with Visual Studio. net on the target system where the application is to be installed. Windows Installer version 1.5 was initially released with Windows XP. If your program is deployed on an earlier version of the system, you need bootstrapper, which can install a new version of Windows installer. Select Windows Installer bootstrapper "Windows Installation Guide" to include bootstrapper in the installation program. During installation, it installs Windows Installer 1.5 before starting to install the target program. The required capacity is about 3 MB.

If you use the Web bootstrapper "web boot program ". After selecting this option, you need to download the URL. You can use this URL to install bootstrapper with the next option. You do not need additional space in the installation package, but the user who installs the application must be able to access the Internet.

If none is selected, bootstrapper is not installed, and Windows Installer 1.5 is not installed on the target system, an error message is displayed during installation.

 

Install Editor:

1. File System: Used to add files to the installation package.

2. Registry: You can create a registry key for an application.

3. file types: allows you to register the specific file extensions of an application ).

4. User Interface: The ADD and configure dialog boxes are displayed during installation.

5. Custom Actions: allows you to start custom programs during installation and uninstallation.

6. Launch Conditions: You can specify application requirements. For example, you must have. Net runtime.