Three major technologies for deploying ASP.net (Next) (2)

Properties that the ASP.net file Type editor allows to set

Property action

Name specifies a type name for the class file.

The application that should be started when the Command user performs an action on the class file

Extensions specifies the extension of the class file

ICON specifies the icons for the class file.

Description A brief description of this type of file

V. Custom Action Editor

Allows other programs to be run at installation time. Custom actions run in the same order as they appear in the editor. You can reorder custom actions by dragging the mouse or by using the cut and Paste commands on the Edit menu.

Six, launch Condition editor

Use this editor to set the conditions that the target machine must meet. If the user tries to run Setup on a system that does not meet the launch criteria, the installer will refuse to execute the program. When setting the launch conditions, we can ask the installer to search the target machine to find out if there are any specific files, registry keys, or components. The Launch Conditions Editor shown in Figure three provides two types of options for setting conditions:

㈠ Search Target machine: Specifies the search operations performed on the target machine, such as searching for specific files, registering keys, and so on.

㈡ Launch Condition: Allows you to check for specific applications on the target machine, such as IIS,. NET Framework, and so on.



Figure Three

The list provided in the following table shows the launch conditions that can be set by the Launch Conditions Editor.

Conditioned effect

The file launch condition is used to search for files that are installed on the target system.

The registry startup condition is searched for registration keys before Setup starts.

Windows Installer Launch Conditions search Windows Installer files.

The. NET Framework launch condition checks to see if the. NET Framework exists on the target computer.

Internet Information Services (IIS) Launch conditions check the version of installed IIS.

Check to see if the. NET Framework is installed on the target machine

As an example, suppose we want to check for the existence of the. NET Framework on the target machine during installation. Select Menu "View" → "editor" → "launch condition", right-click "Requirements on target computer", and select Menu "Add. NET Framework launch condition" so that the. NET Framework launch condition is set. When a user attempts to install an application on a machine that does not have the. NET Framework installed, the installer prompts the user to install the. NET Framework to continue the installation.

Vii. User Interface Editor

As the name suggests, the role of the user Interface Editor is to set the sequence that appears in the User Interface dialog box during installation on the target machine.



Figure Four

As shown in Figure four, the user Interface Editor contains two types of installation modes:

⑴ Installation: Lists all of the dialog boxes that will be displayed when an end user executes the setup program.

⑵ Administrator Installation: Lists the dialog boxes that will be displayed when an administrator uploads the installer to a network location and then executes the installation.

In Setup and administrative installation mode, predefined dialogs can be grouped into three categories:

⑴ Startup dialog box: A dialog box that appears before the installation begins.

⑵ Progress dialog box: A dialog box that displays the progress of the installation to the user.

⑶ End Dialog: Displays a dialog box that has been successfully installed so that users can start the application through the dialog box.

Adjust the User interface dialog box display sequence is convenient, as long as drag and drop the dialog box to move to the appropriate location. Even without configuration, a set of default dialog boxes shown in Figure four always appear during the installation of an application.

Add a splash screen

In the user Interface Editor, we can easily add additional dialog boxes to be displayed during installation. Right-click the Startup node, select Add dialog, and in the Add dialog window, select the dialog box that you want to add from the dialog list, that is, splash screen, see figure Five. After adding the dialog box, we can use the drag-and-drop method to adjust the display time.



Figure Five

Since the splash screen always appears at the beginning of the installation, we'll drag it to the front of the dialog sequence. In the splash screen window, we can display a bitmap and add a bitmap by right-clicking the "splash screen" node in the user Interface Editor and selecting the Menu "Properties Window" to set the value of the SplashBitmap property to an appropriate graphics file (BMP or JPG file).