How to: add files when installing the installation package in InstallShield

Original article: How to: add files when installing the installation package With InstallShield

I always thought this was not a problem, but I did not expect many people in several groups to be confused about how to add files to the installation package. Today I am a little overwhelmed and have compiled an article for your reference.

First, I want to say it again in a loud voice: Don't talk to me any more about English !!!! When you are a programmer, you have to make yourself understand English !!! If you can't understand it, just change it! Merged in this line! There are also 4000 or 5000 bricks to be moved to the construction site! It's no better than getting two thousand yuan while complaining! Google duaiang provides translation functions for free! Stop chatting with your sister! Sister is not a translator !!!

Take installscript project as an example:

Open an installscript project and find the Application Files item on the Project Assistant page. Here is the place where you can add files to the installation package in the Wizard assistant.

By default, you will see that the option in the first drop-down box is all application data. Click this drop-down box to display all the defined feature items. Is allows users to add different files for different feature, so here you can select feature as needed and then add the corresponding file ---------- if you do not understand this sentence, then select the default item all application data.

In the big box in the middle, the total node is the destination computer. If you don't understand it, close your laptop and drop it out of the window!

The following nodes are explained one by one:

Script-defined folders: This is a custom path. What is the purpose? Baidu "InstallShield multi-path installation", you will be pleasantly surprised. This path is used to provide users with an extra selectable path. Do not understand? For example, if you have a software, a client, a server, packaged in an installation package, and you want to install the client, you have to let the user choose where to install it; the user also needs to install the server, and you have to let the user choose where to install it. Therefore, you have to provide two pages, one of which is the client page, with the path selection function, one is the server page, and the path selection function should also be available. Do you understand? Read it three times.

 

Application target Folder: this is the core path of the installation package-the target path targetdir, which is expressed as [installdir] in basic MSI project and installscript MSI project. If you want to create a simple installation package without any bending, the file must be added in this place. This path allows you to select the installation path during actual installation. For basic MSI project and installscript MSI project, instslldir is usually displayed under programfilesfolder. It doesn't matter. Add the file to instslldir anyway.

Many people do not know how to use the path selection interface during installation for the first time. For more information, see my other blog post.

How to: How can I see the select path interface for the InstallShield installation package?

Http://www.cnblogs.com/Cindy_weiwei/archive/2011/02/22/1961244.html

 

Program Files: this is the famous c: \ Program Files. I don't know why many people add the file here when they first install the installation package, and then cry that the installation package cannot select the path, is it because the default path of most installation packages is c: \ Program Files, which mislead everyone? This path is a dead path. The files added here will always be installed only under c: \ Program Files, more specifically, on the System Disk \ Program Files; this path must exist as long as the windows system is operating normally. Therefore, the default path of the installation package must be this. Many people may want to say that, for example, if I want to fix the path to drive D, I think it is not desirable because you cannot ensure that drive D is always present, but the system disk must exist.

 

Program Files (64-bit): Needless to say, the meaning is the same as above, but it is only the program files in the 64-bit operating system; note that in the 64-bit, the path above will become the system disk \ Program Files (x86)

 

Support Folder: supportdir in the script. The file added below will not be installed on the target machine. The file is only valid during the installation process and can be further operated in the script.

 

Windows: The three paths below are all system paths. If you don't talk about them much, they are all dead paths. Select them based on your actual needs.

 

 

--------------------------------------- I am a split line -----------------------------------

 

Let's talk about the basic MSI project and installscript MSI project.

 

Appdatafolder: The application data folder of the current user. For example:

C: \ winnt \ profiles \ USERNAME \ Application Data; this is the dead path

 

Commonfilesfolder: the common Files folder in the system. This is the dead path.

 

Programfilesfolder \ my product name [installdir]: This is the target path of the installation package. If the installation package is normal, add the file here.