Packaging software usage

Packaging software usage

Originally, it was the most important thing for me to develop programs and the process. After the development is complete, it doesn't matter if you choose a package software and package the software at will, however, from the convenience, functionality, friendliness, and defect of several packaging software packages used in the past few years, we still have to choose a good packaging software. A good software development is complete, why should your software be eclipsed by the final joint ?! Here, I will explain the quality of several packaging software based on my experience in packaging software!

First, I have used the following packaging software: install shield, Advanced Install, and SetupFactory. Here, install shield is used during founder's time, advanced Install is used by a security company in Shenzhen, and SetUpFactory is used now, from the usage experience, the order I use also shows my views on the advantages and disadvantages of packaging software. Although they are all foreign packaging software, I personally think that from all aspects of the software, SetupFactory is better than Advanced Install, and Advanced Install is better than Install Shield;

Install shield is the packaging software I initially used. Founder's colleagues have always told me that it is very powerful and supports custom scripting. Since it was only used to this packaging software, I have always thought that this software is very good and has very powerful functions, but I was using it but I felt that the operation was complicated. Many operations do not know where to add or delete them, of course, the basic configuration is met, but it is difficult to implement custom operations. writing scripts is not semi-automated. You need to learn the script language to complete the custom operations smoothly.

The Advanced Install packaging tool is a packaging software that I used after the completion of the North drift. Of course, it is related to my work experience and is also the packaging software used by my colleagues, I found that South China tends to use the Advanced Install tool, which may be the cause of this feeling. It should have little to do with the region. When I used this tool for the first time, compared with the first tool, I suddenly felt that it was really good. Why? In fact, it is not the basic operation that should be used for packaging, but compared with Install shield, the packaging software interface layout is simple and friendly, divided into the left and right sides, all the functions are listed from the left, the list of Install shield functions is deeply nested and sometimes difficult to find, so from the perspective of usage: straightforward and clear; friendly operation interface is far from attracting me, of course, this guy also supports adding scripts. The only feeling is that it is as difficult to use as Install shield. The time to use Advanced Install is relatively long and many problems are found: user-defined operations do not work; the system compatibility is poor, and the installation package is run in the same system as some customers; the previously saved configuration may be lost after a new file is added in the middle, you need to reconfigure one by one. There is no problem with UI layout, but the layout is not completely arranged according to the installation sequence. The operation seems to be lacking. Of course there are many bugs, for windows Service, batch processing, script, multi-language, and multi-package organization After many problems, my impression on it was greatly reduced. I always wanted to change the idea of packaging software, but I never found any good packaging software, so I never dared to change it.

Later, after packaging the software, I found many questions about packaging software. A test colleague suggested that I replace it with SetupFacotry, I tried to install this software, but I have never used it because I am not familiar with the software and have a tight schedule, however, as the project goes on, the number of packages is one time, and each bug library inevitably raises these packaging problems. In addition, the system is too large, components or packages are too large, and there are many custom operations, therefore, we still decided to change the packaging software. After a period of study and consultation, we finished the first package, and the software that the customer could not run on the machine could also run, this makes me feel much better, and it is much more convenient to package. Advantages compared with Advanced Install:

(1) The UI layout is the same as that of Advanced Install, but the layout order on the left makes me feel very nice and is carried out in accordance with the software installation order, so I want to change which step can be quickly located;

(2) All components used by the project are displayed on the right side. These components can display all or the components you want to see through the filter above, such as all, packaged, unpackaged, exe, or self-compiled filters, such a large project can be managed and browsed in a unified manner by hundreds of thousands, you can also quickly locate and operate a component (such as shortcuts, attributes, and packages );

(3) The file order on the right is based on the folder order, rather than the messy one. Why? You can select all the components in a folder and click Properties to classify all the components in the changed folder into a package. This is a major weakness of Advanced Install, in the "Organization" function, Advanced Install needs to create a new component package or package, and then drag the component into the package one by one. You can think of thousands of packages, but you cannot drag multiple components into the package! Drag the components one by one. The biggest problem is the bug. adding a new component package to a new component does not classify it into a folder. You must remember the new components you have added, drag the package to the package one by one. Otherwise, you can choose to install the package to another package and the package cannot run! This is the most disgusting thing. I have encountered ten times !!! In addition, You must select "current operation package" for all its operations. To operate on another component package, you must switch the package at any time. Otherwise, the components in the component package are not displayed in many places, ah, I want to kill people.

(4) multi-language support is better than Advanced Install. People who have used Advanced Install should support it. To support multi-language support, you must modify the language tables in "Translation". Of course, this is normal, otherwise, how does one support multiple languages? But the problem is that many fields cannot be modified! Who can afford an English Chinese character for TMD Chinese installation? SetupFactory is in place and there are multiple sets of languages for shortcuts. Advanced Install does not know where to support multiple sets of shortcuts in multiple languages, which is disgusting!

(5) The operation interface function is more direct and simpler than the Advanced Install function, and it is easy to find the modification content you need. Even if you do not know it, you can find the menu or button by pressing it back and forth;

(6) user-defined operations are often very gray, and the difference in Advanced Install is far away. I feel that their programmers and SetupFactory programmers are not of the same level, and they write too much difference, the most custom operations I use are file operations, registry, windows Services, and bat batch processing. All these operations contain semi-automated script editing, I don't need to write a specific script at all. I select the corresponding operation. After confirmation, the script is automatically generated and n operations are supported. I don't want to talk about it. I have to give it a thumbs up !! In contrast, Advanced Install is far behind. There is a "Custom operation" module, which has a bad layout, meaning module, and execution problems. It keeps reporting errors and Spam !!

In my opinion, I will teach you how to use SetupFactory. My requirements are as follows:

(1) installation: select path-select package (Select installation component)-finish-create server-Run batch processing

(2) uninstall: Run batch processing-Stop deleting service-delete the Start Menu directory and folder

(3) Others: Change the packaging ICon to custom, Installation Style or style

First, let's take a look at the packaging process:

Add my package project as follows (to show you the specific structure and components, I will expose my platform name and organization here ):

Batch) and two batch files, one is the batch processing after the installation is completed, and the other is the batch processing that needs to be executed before the uninstallation.

(1) Open SetupFactory. Here I use the 7.0 cracked version. Select the "Create a new project" Wizard and follow the Wizard to complete the basic packaging process step by step.

(2) enter the company, software name, and company website, and click Next.

(3) Select the folder path of the package and click Next.

(4) Select the window style. By default, click Next.

(5) select the theme style of the window. Select the theme style as you like and click Next.

(6) Select language support. Select the Chinese Language and English Language. Set the Chinese language to the default value and click Next.

(7) Select the subordinate technology vb version. We do not need to select it. click Next.

(8) Select the supported OS versions. By default, select all. Click Finish. The basic projects are automatically created.

(9) Basic interface for final creation

(10) If the file is incomplete, you need to add the file. in the left column, you can edit the attribute of the file in the first section. Next, modify the version information, select Settings in the second section --> session settings. All the configuration options with tabs for the edit section are displayed, and the session settings option table is selected.

Set the product name, product company, and copyright. You can modify the default AppFolder, that is, the default application installation path and the default application shortcut path folder;

You can modify the background style and select the background tab:

Select the "Display Background window" check box to make your favorite color or use a texture directly;

Change requirements:

Change the supported operating systems. The supported operating systems are rich and powerful. Keep the default configuration;

Logs:

This is the installation log tracking to facilitate Error Tracking and keep the default value;

Advanced:

Here we can use Silent Installation. Here we do not need Silent Installation. You can modify the installation level to the current user or all users. You can modify the default packaging icon, here I use a custom icon to replace

(11) separate package components (custom installation package)

The remaining three items in the settings are security, package, and language. For security, there are serial numbers and other configurations. skip this step and the language is multi-language configuration, which is very simple. The focus is on the package;

Package: This is the component package. During installation, the user selects to install those component packages instead of all components. Click the "package" function.

Here I have created seven package based on my initial needs, which can be installed and used independently. When adding the package, select the "add" button:

Enter the package Id, component name, and description, switch to the English language, and enter the corresponding component package name and description. The ID is shared. To avoid errors, it is best to use English for the ID, click OK to add the package. to modify the package, select edit.

(12) assign specific components to the package (Component package)

After the package is created, you must classify the corresponding components into the corresponding package. Let's look at the file list on the right.

I like the sorting here. It is sorted by different component packages (my component name is also based on my project folder name). We select the corresponding component, right-click the file attribute menu in the menu.

Select the "package" tab for the multi-File Attribute. This tab displays the names of all the packages we just created. You can select the corresponding package, in this case, all the files we just selected will be packaged into the AlarmServer component;

Similarly, we can allocate all the components to the corresponding package. At this time, all the components change to the packaging status. If not, the components are not in the package status.

After the package is assigned, We need to display the package before installation (only one package is available by default, so this dialog box is not displayed. You need to add a dialog box)

Before installation, delete unnecessary user protocols in the pop-up dialog box, add the "select package" dialog box, and move it to the specified location (through the upper and lower buttons ):

Move the component package created and allocated on the right to the left Tree. Click OK to complete the package. This dialog box is displayed during installation;

(13) create a shortcut for the corresponding exe

Because there are more than 5000 files on the right, too many, we just need to create a shortcut for exe, select a filter, filter the files on the right

Double-click a component:

In the pop-up file properties, select the "shortcut" tab and select the application folder in the desktop and start menu to generate a shortcut. Of course, you can customize the location where the shortcut is generated, click "OK" to generate a shortcut for this component. Similarly, if other shortcuts are generated, a shortcut is generated for both the exe and batch processing by default. If this is not required, remove the check box;

After all shortcuts are generated, the "Shortcuts" column of the file list contains the corresponding information.

(14) style Modification

In the Screen Bar, select a project topic. We can modify the style or topic we need, or even modify our own skin library.

It is easy to retrieve the module by yourself. I will not introduce it here.

(15) Establishment of windows Services

Because my project has a windows server and the windows service must be installed after the installation is complete, select "Install" on the left-side screen (that is, the installation of all dialog box screens). The dialog box is displayed:

Select "End installation" and click "edit" to click "finish" (next:

When setting the file path, the path of the selected file must be referenced. Therefore, if you use the variable, select % AppFolder % variable and Expand the variable path with SessionVar. Expand () to obtain the full path. The server path here is as follows:

SessionVar. Expand ("% AppFolder % \ NVMS_Service.exe"); automatically generates the corresponding automatic script after the addition is complete. Of course, familiar users can directly use the code without any operation;

File operations can be the same. We will not introduce them here. Of course, the system supports system operations (restart, shutdown, etc.) and file operations (mobile, command, delete, run, etc), service operations (create, delete, pause, restart, etc)

(16) Build settings and build

Create an exe package and set the path and name of the production package.

(17) Installation results

The next step is to complete windows service installation and bat processing.