A Preliminary Study on installing the. Net Program Using InstallShield X-Express Edition 10

Today I learned how to package a project in InstallShield x express edition V10 (is X. In order to deepen your understanding and memory, and help others who are new to it, we will write down the key points in use. Is x supports two running modes: independent running and vs. Net plug-in calling. After comparison, I think the first method is more intuitive and easier to modify control options. So I will introduce the example in this way. Because it is not long before I use it, it is inevitable that there will be errors and omissions. So please tell me if you see any mistakes ~

[Key Aspect 1]: Create a. net installation project

When creating a project, you can see that there are "Express project" and "Visual Basic. Net wizard" and other project types. The difference is that the express project uses is X as the IDE and can set all the installation parameters. The Wizard project just helps you call out. to add a new installation project in the specified solution. Here I select the former.

[Key aspect 2]: Create an installation project that fully supports Chinese Characters

By default, the new project only supports English. The support for English here is not to say that other non-English characters are not allowed at all, but in some settings, if a string containing full-width characters is used, the strings will automatically become question marks. To avoid this problem, you must set the project language to "Chinese (simplified)" to create an installation interface in Chinese )".

[Key aspect 3]: scanning dependent files

When the program file in "application filesfolder" is used, a dialog box will pop up asking you to scan the dependent files of .exe or. dll. If the added program file needs to call other library files, select "yes ". The dependent files discovered by the scan will be automatically added to the installation package. Note: Is X does not regard the system library in. NET Framework as a dependent file, and regards. NET Framework as an integral underlying environment. For this reason, if you want to include dotnetfx.exe in the installation package, it is not implemented by adding a file. The specific implementation method is described below.

[Key Aspect 4]: Creating shortcuts

You can create various shortcuts in "application shortcuts. If the program file contains EXE, is X automatically creates a "launch xxx.exe" shortcut. Note that there is a "Shortcuts" link in the "Other Place" area on the left of the window. This link can be switched to the detailed attribute setting interface of shortcuts. In this interface, you can set the working directory of the program. Unlike developer, is X sets the working directory as the installation directory by default. I think this is a more user-friendly consideration.

[Key Aspect 5]: Enable the dialog box asking about the installation path

By default, is X disables the dialog box that asks the user in which directory the program is stored during installation. To enable this dialog box, select the corresponding ticket in "installation interview.

[Key Aspect 6]: generate the installation package

After you configure all the items related to the program, you can generate the installation package. If you want to facilitate distribution, we recommend that you package all the files into an EXE. To achieve this, select "single executable" in "build installation ". This option actually corresponds to the "singleimage" generation method. After selecting the generation method, do not rush to "build installations". There is another very important step.

[Key Aspect 7]: the installation package contains the. NET Framework 1.1 Chinese version.

To package dotnetfx.exe in the Chinese version, and enable the installation package to automatically check whether the client needs to install it. Packaging This step requires a little trouble. First, set the location and version of dotnetfx.exe in the corresponding generator formula (singleimageexample of release.

Then, select the language version of dotnetfx.exe. If you want to use a non-English version, you must download it through the "download more than ages" button. Fortunately, the official server of is X is much better than wise, and the download speed is very fast.

We do not need to worry about checking the client. As long as the installation package contains the. NET Framework, the environment will be automatically detected during installation.

[Key Aspect 8]: The error code "-6247" is returned when the installation package is generated.

The error cause can be described in the error description, but I think this may be a bug. The solution is to delete all the shortcuts created earlier and recreate them, so the-6247 error will not occur in the future.