A complete InstallShield installer instance-goddess of the sea of azelas (2)-Basic settings 2

Original article: a complete InstallShield installer instance-goddess of the sea of azelas (2)-Basic settings 2

Previous Article: a complete installer instance-goddess of the sea of azelas (1)-Basic settings 1
7. Click application files on the Guide Bar.

Here we will fine-tune the installation path and specify the file to be installed for each feature

Here I don't want to use the program files | company name | product name path. I want to use program files | product name. I directly click my product name [installdir] and drag it to programfilefolder, you can also change my product name to the folder name you want.

Next, specify the file to be installed for each feature.

Open this drop-down list, where all feature files are located. Create a folder for each feature in order and import the required files.

Select the first feature, that is, server, click the my product name [installdir] node, right-click, and choose new folder from the menu to create a folder.

Create a server folder to store the files required by the component.

Create an icon folder under the server folder to store the icons used by the component.

Then add the file to be installed for the feature.

The icon folder we created here is used to store the icon used by the feature to create a shortcut later. Add the corresponding icon file to this icon folder, and remember the source folder of the icon file, which will be used later when setting shortcuts.

Click the folder to add files, click Add files in the lower right corner, and then add files

Next we will add a folder for the feature, if all the files in this folder are required for this feature. The benefit of adding a folder is that as long as the folder location and name remain unchanged, the files in the folder are dynamically loaded and the file name changes do not need to be considered.

Click the folder to be added, click Add folders in the lower right corner, and then add the folder.

Select a folder and click OK.

I will ask you if you want to use dynamic file links. I have chosen to confirm the advantages of the above.

The source folder is displayed. If this folder contains subfolders and needs to be added together, check the include subfolders option.

Some simple settings are allowed to include or exclude some specific files. Wildcards are supported.

Click OK to add the folder.

Create a folder for each feature and add files.

Document Feature, except for the icons used by the file, should not be added. Later we will use the real-time copy method during installation to copy the document.

8. create shortcuts for executable files.

Click application shortcuts on the Guide Bar.

Click new to create a shortcut

Select a feature to create a shortcut.

If you want to create a program in a non-.exe format, select all files (*. *) as the file.

The installation target path of our program is set under program files. Therefore, double-click [programfilesfolder] to open it and click to enter it.

Here we need to create a shortcut for client. bat, because this is the batch processing file used for startup.

Installshieldcan automatically monitor the existence of the. exe file and automatically generate shortcuts. You only need to make some necessary modifications.

The newly created shortcut will appear here. The name is not nice, and it looks bad. We will change it to a name and an icon.

Select a shortcut, click rename, and change the name of the shortcut.

Note the options on the right.

Create shortcut cut in Start Menu, a shortcut is created in the Start Menu.

Create shortcut cut on desktop: A shortcut is created on the desktop.

Use alternate shortcut cut icon to replace the shortcut icon

Associate a file extension with the specified cut's target, no use, do not know what it means.

Here we will only create a shortcut for the Start menu, so select the first item.

Check the third item and click the Browse icon.

Recall that when I added a file for the feature, the corresponding icon was added for each feature. Here, set the browsing folder to the folder you just used to add icons. In other words, where did you add an icon to feature, where to add the icon now.

In fact, I have been very puzzled about this. I didn't know how to select the icon at the beginning. I added an icon from any folder outside, so that I couldn't find the icon after packaging, after the experiment, we learned that the selected icon file should be copied and packaged into the installation file. Visual Studio can't help but mention this. Although this tool is generally used as an installer, it still has a good idea. When its components specify to copy the icon file, when creating a shortcut, the icon used by the shortcut points to the icon file under the virtual installation target path, rather than specifying the actual source folder. This difference reflects the ideological difference.

For example, you can specify shortcuts for each feature, except document, because nothing except the icon file is added to this feature.

Now we have added shortcuts under the Start menu for each executable program.

Switch to installation designer and find System Configuration | shortcuts.

You can see that the shortcut exists in the form of company name, software name, and shortcut in the Start Menu. As a matter of fact, I don't like this kind of form. If you want to open another layer, it's better to make some changes directly.

Here I changed the settings as follows:

Don't tell me you won't change it. Just drag the test folder to the next plug in the program menu (that is, the "All Programs" under the Start Menu) and delete the extra company name folder.

9. Some people may have noticed the attractive words "Create an uninstallation export cut" under "more options" on the Left bar on the Project Assistant Interface.

However, I want to tell you that if you choose this method to set up the uninstall shortcut, you will find very frustrated:

A) It seems that this uninstall shortcut will only appear when a feature is installed (of course, the default feature, this form of feature determines that each file or shortcut must belong to a specific feature). Therefore, when your customers only choose to install other feature, this uninstallation method does not appear, but it must be uninstalled in "Add or uninstall programs ".

B) if you write a script so that some external files will be copied during installation, these files cannot be deleted in this uninstall mode. (If you really want to save these files, you can set them to permanent in the script. This attribute ensures that you cannot delete these files in any unmount mode ).

Therefore, we ignore the existence of the uninstall shortcut, and will use a script later to achieve the perfect Uninstall.

10. Click Application Registry on the Guide Bar.

Write keys and key values to the Registry. Ignore them because this project is not required. It is not difficult for anyone in need to obtain relevant information.

11. Click installation location on the Guide Bar.

This is the language used to set the installation package. After multiple languages are selected, you can select the language used for installation at the beginning of the installation interface. However, as a company product, the customer's impression of being so lazy is to be compromised, so select a single language. The installation packages in which language are different from the installation packages in which language.

However, you may be frustrated to find that if you want to select another language as the default language, it seems that an error has been reported.

It took me a week to solve this problem (of course I had access to InstallShield at that time, but I still had no idea). I finally asked the technical support staff to solve the problem.

Switch to installation designer and find installation information | general information. What is displayed under string tables? Yes, all the languages you selected are listed. Right-click the language you want and choose make default and OK, switch back to project assistant and remove all unnecessary languages.

The default language is English.

12. Click build installation on the Guide Bar.

I have never used this option to set the package and installation disk. I use the release wizard on the toolbar.

Now, the first part is basically complete. If there are some installation packages without special requirements, this part of the content is enough to do a basic installation package.

Next article: a complete installer instance-goddess of the sea of azelas (3)-advanced settings 1