VB.net Program Packaging Release

This article is mainly about what I do in the computer room fee system vb.net version of the packaging release process, the text is basically composed of pictures, the text is actually quite a lot.

First of all, I read the article before writing this article. vb.net packaging release, WinForm packaging release diagram, vb.net WinForm program simple packaging and Deployment--< computer room toll System >. OK, edit the number of blog 1, blog 2, blog 3.

On the concept of WinForm, Baidu Encyclopedia. WinForm is a title to Windows Form in the. NET development platform.

I've packed a total of 3 setups here, named Setup1,setup2,setup3. As a result of Setup1, there is no screenshot, the screenshot is from the packaging Setup2 began, so this article describes the Setup1 packaging of the figure is Setup2. If the other operation is the same, it will not map.

Then my computer room billing system, using Visual Studio as a tool to write development.

1. First, if you want to know the difference between release and debug debugging, look at the top half of the blog 1.

2. Then, if you want to know the next few installation and deployment, you can see the middle part of the blog 3.

3. After the above step, the interface will become like this (pictured below), and then

4. Then, select Setup1 (imagined), right click, add-project output (imagine).

5. Then you add the project output group interface, which is available on the step diagram. When you are sure, you will see the application folder (the first folder) in the figure in step 3 above, with many DLL files in the Setup1 (imagined) directory.

6. Then right click on Setup1, select Build, and in step 4, you can see the build (U). Then wait a minute, the lower left corner of the interface shows that the build is successful and you can find the installation package in the release of Setup1.

Note that when the build is finished,

Steps in the installation process

7. Can be installed on the spot, my installation is off-site installation. So the interface is different.

8. Next, Next, choose the default is good.

9.

10.

11. Due to Setup1, there are some operations did not do, so run, the desktop is not anything, and then to go to the installation path to find EXE file, click to run, you can run correctly.

The following are the operations of Setup2 and SETUP3, which are similar to each other, but the installed program succeeds, executes correctly, fails, and does not connect to the database. (see below, you can take a look at blog 2.) ）

The previous 3 steps and the above, is the 4th step, the choice is the file, and then it is their own to select files required files, the general need is the DLL file and EXE file. Then the difference between the two steps is (illustrated in the following illustration), and then it's the same from steps 6th through 10th.

The additional actions are then made for the packaged publication. shortcuts and uninstall . Blog 1 and blog 2 are introduced. Blog 1 on the uninstall introduced, but relatively concise, blog 2 on the shortcuts and uninstall the introduction of the more clear.

First uninstall, or Setup1, right click, add, File, in C:\Windows\System32, directory, press MSIEX, you can quickly find the Msiexec.exe application. It can be used to uninstall the installation of a good computer room fee system program. Drag it to the application folder (the first folder), as mentioned earlier.

Then right-click Msiexec.exe and create a shortcut. Change the arguments for this shortcut to "/x {Product ID}", and the value of the product ID is the ProductCode property value of the packaged project Setup1.

11. After installation, the interface will have the two files. Double-click the ChargeSystemVN.exe shortcut, and it's OK. Click on the Msiexec.exe shortcut to uninstall the program.

Finally, my connection database statement uses a configuration file that can be added to the file when I add it, and then I can modify the configuration file as needed. But I forgot to try it. .......