"C #" VS2012 Installation and deployment How to package a program

This is required for packaging: InstallShield Limited Edition for Visual Studio. about how to download the installation on their own Baidu bar, I will not write.

InstallShield Program Packaging diagram

The packaging tool in VS2012 is considered an assembly, and is created under the program solution as it is used with the assembly. What we need to do is add the item. But for first-time friends, we need to download and install the packaging tool as prompted. Specific installation methods are no longer detailed, many online information.

1. Set the Setup assembly InstallShield after the installation is complete, perform the following steps right-click on the solution-- Add-new project--and other project types--Installation and deployment , as follows:

Next

2, the Publisher must select the publication before proceeding to the operation, set the default path of the publishing folder to the folder where the system is installed in the properties of the startup project. Because we are packing the magic mirror system, right-click on this item.

And then you see this:

As shown in the second circle: the last Setup1 in the path is the directory I just created to install the deployment assembly. This needs attention.

3. Set Program Installation Information

Application Information Main Setup program in the installation of some information about the program, such as: Program developers, program development company, program installation icons and program introduction and so on.

Among them, 2,3 can fill in according to own idea. Click 4 to enter the

Follow the language and change to Simplified Chinese. The other options on this page can be explored on their own, can be changed.

4. Add Program Files

In a few steps to add a program file will have the main output, the source file and other options box, in fact, its generation mechanism and. NET program is the same as the compilation mechanism. The fifth part of the UI. Main output, after the installation file is generated, the package contains reference files for other layers that interact with the UI layer, but not the components that are not connected to the UI layer (the boot layer), and we can only add them manually.

Note: If your fourth step is blank. The first big step in front of you is a mistake, and no installation deployment is added to the solution.

Then select the main output of the magic mirror system. You see the Circle 5. Ring 7 is a DLL file and a configuration file, because I want to read and write hardware, so these are also I have to. Click on the ring 6 to add these two files to the ring 7. Circle 8 is my "right button-new" folder on lap 2, which stores pictures of my system. You can also create a folder according to your own needs.

5, add the program's resource file program source file is the program to run the resource file, also contains the program's source code files. If you do not need to package the source files, this step can be omitted.

6, set up the installation registration file if a third-party control is used in a program that is being developed, it is often necessary to register it with the target system during installation, and the same install also provides this functionality for the user. Install can by setting the DLL file or OCX file registration, first to add the registered files, and then by setting the file installation properties to specify whether or not, set such as. (right-click on the DLL file-properties)

7. How to open the design program

Application Shortcuts program shortcut open mode, install to provide users with two kinds of display, respectively, the win menu and desktop. Displays some of the settings ' notes, which can also be used to set the program's display icon.

Keep the dots in the loop 3 until you find this: double-click when found.

And then you see this:

Circle 1 can be renamed, such as "Magic Mirror System", here I am not renamed, Circle 2 is the Start menu to create shortcuts and create shortcuts on the desktop.

Attention:

And then you see this:

Then create a shortcut to uninstall the program

8. Set the program installation registry key The application does not need to consider the program's registry key when installing, this step may not be set.

9. Set the installation view when the program is installed

Design according to your own needs.

10. Packaging Environment

After setting up the above steps, our Packager basic setup is complete, but in some cases we tend to package the. NET environment or other programs required to run the Windows environment, install also for our good design of the environment packaging. When choosing the environment to be packaged, be sure to pay attention to the name of the file, usually need to directly put the environment installation package in the installation EXE when we want to select a file named full, such as I want to integrate the. NET Framework 4.5full Complete installation package into the EXE, At this point I'm going to select the Microsoft. NET Framework 4.5 Full and then wait for vs to download the installation package for that environment to the Assemblies folder. (Note: This thing is to download, the download time depends on your network conditions, the network may not be able to download the bad) in addition, it is important to note that after the name of the (Web Download) parentheses The content of the description file is just a link, A network download is required for installation to complete the installation.

11. Release procedure

The above installation steps to build the solution, but the resulting file will be placed in the DVD-5 folder, you want to use the installation file, you must copy the entire folder or the installation will be wrong, so the content is very cumbersome, and the installation experience of the customer is very poor, there should be other solutions, yes, As shown, we will use Singleimage's installation package to integrate all the files into a single Setup.exe, which requires only one Setup.exe to install again.

If there is no packager running environment in our installation files, the above steps are sufficient to satisfy the requirement of only one Setup.exe, but the steps must be passed if the installation environment needs to be packaged into Setup.exe.

OK, after the setup is complete, the next step is to build the solution (this is no, right-click on the project) or just generate a single assembly, when the installation file is only a setup.exe, such as.

After you have finished the above steps, the package basic setup is complete, and the next step is to build the solution. After the solution is built, a folder named Setup is generated under the installation assembly, and the installation files are saved in the following directory. Install after generating the installation files will have Setup.exe and. msi two installation files, EXE files are installed boot files, the core file is an MSI file, which contains the program's components.    Locate the Setup.exe file and the MSI file inside to install it.

Finally, it is important to emphasize that the Install Packaging tool does not inherit the Chinese environment, there is no Chinese language in its underlying language library, so the solution, assembly name, etc. related to the main output of the file is best not to name the Chinese name, or the following error will appear: " -7184:the FileName column of the file table includes characters that is not available on code page 1252 ", the error is described in code snippet 1252 where no discovery and file name related 's Language library.

Write at the end: If you need to build a solution that installs the deployment (package) more than once and then regenerate it again before rebuilding it, "right-clean" on the solution, or you will get an error when rebuilding. If you have an error while cleaning up, then clean it up again, usually without the error.

Not very important, we can find out for ourselves.

To a foreigner's operation video http://resources.flexerasoftware.com/web/demos/IS2010_VSLE_Demo/IS2010_VSLE_Demo-lite.html can refer to the reference

In a few days I will also upload a video that will demonstrate the entire operation. Although it is not difficult to pack, but do not delve into it is not good to fix. After all, there are so few videos in this area.

"C #" VS2012 Installation and deployment How to package a program