After a long period of development, VB. NET has become very familiar to many users. Here I will share my personal understanding and discuss it with you. Here we will give you a question about packaging VB. NET.
As an upgraded version of VB6, VB. NET has many new features that allow you to easily and quickly create. NET applications (including XML Web
Services and ASP. NET web
Application), or a powerful object-oriented programming language (such as inheritance, interfaces, and overloading ). The new language features include free thread processing and structured exception handling. VB. NET
Fully integrated with the. NET Framework and public Language Runtime Library,. net
The framework and the Public Language Runtime library provide language interoperability, garbage collection, enhanced security, and improved version support. It can be said to be an epoch product!
From VB6
In the development of VB. NET, form applications are always an eternal topic. Any Windows application is closely related to the form. In many cases, we need to perform some operations on the form.
For special settings or operations, this article uses VB6 and VB. NET to describe the special problems and solutions of form applications, as well as the new functions that VB. NET brings to us!
VB. NET package process Introduction
:
1. Open the windows application.
2. In Solution Explorer, right-click windows
Application solution, point to "add", and click "new project ".
3. In the "Add new project" dialog box, select "Install and deploy Project" in the "project type" pane, and then select
"Installation Project" in the "template" pane ". Click OK.
4. In solution resource management, right-click the installation project, point to "add", and then click "project output ".
5 In
In "add project output group", select "primary output" and click "OK ". All dependencies, such as managed. MSM, are automatically added.
6. In Solution Explorer, right-click
Install the project, point to "add", and click "Merge Module ".
7. In the "add module" dialog box, select the following modules to be added to the installation project, and click "open ":
- Managed_chs.msm
- Database_access.msm (my machine is crystal_database_access.msm)
- Database_access_enu.msm (my machine is crystal_database_access_chs.msm)
- Regwiz. MSM (my machine is crystal_regwiz2003.msm)
- Vc_crt.msm, (my machine is vc_user_crt71_rtl_x86 _ ---. MSM)
- Vc_stl.msm (my machine is vc_user_stl71_rtl_x86 _ ---. MSM)
(If the windows application you deploy uses the ADO. Net dataset, you also need to include the vc_crt and vc_stl merging modules)
8. In Solution Explorer, right-click the regwiz. MSM file and select "properties ".
9. In the "properties" window, expand
Mergemoduleproperties, and then enter a valid license key (aap5gks0000gde100ds) in the "license key" attribute box ).
Note that the license key must be provided whenever the Crystal Reports application is deployed. (6 and 7 are the packaging process added when the program uses the crystal report)
10.
Select the application folder, right-click, add/file, and add your program file (connection in BIN), such as EXE file and Access database file.
11.
In the Application folder, create two shortcuts for the master output and rename them. Add the two shortcuts to the "user program menu" and "User desktop" respectively ". Add icons for shortcuts.
12.
Set the attribute alwayscreat of the three folders in the file system to true.
13. Solution for generating package
Added the uninstall function during VB. NET packaging.
:
1. Upload the msiexec.exe file in the package object (generally found in C:/Windows/system32)
2. Select an application in the file system administrators
Use the program file, press "right" on msiexec.exe, and select "Uninstall" to create a shortcut. Rename the shortcut to "Uninstall ".
3. Change the arguments of this shortcut
Is "/X {product ID}", and the value of product ID is the productcode encoding value of the packaging destination.
<! --
/* Font Definitions */
@ Font-face
{Font-family:;
Panose-1: 2 1 6 0 3 1 1 1 1 1;
MSO-font-alt: simsun;
MSO-font-charset: 134;
MSO-generic-font-family: auto;
MSO-font-pitch: variable;
MSO-font-Signature: 3 135135232 16 0 262145 0 ;}
@ Font-face
{Font-family: "/@ ";
Panose-1: 2 1 6 0 3 1 1 1 1 1;
MSO-font-charset: 134;
MSO-generic-font-family: auto;
MSO-font-pitch: variable;
MSO-font-Signature: 3 135135232 16 0 262145 0 ;}
/* Style definitions */
P. msonormal, Li. msonormal, Div. msonormal
{MSO-style-parent :"";
Margin: 0 cm;
Margin-bottom:. 0001pt;
Text-align: justify;
Text-justify: Inter-ideograph;
MSO-pagination: none;
Font-size: 10.5pt;
MSO-bidi-font-size: 12.0pt;
Font-family: "Times New Roman ";
MSO-Fareast-font-family:;
MSO-font-kerning: 1.0pt ;}
A: Link, span. msohyperlink
{Color: blue;
Text-Decoration: underline;
Text-underline: single ;}
A: visited, span. msohyperlinkfollowed
{Color: Purple;
Text-Decoration: underline;
Text-underline: single ;}
/* Page Definitions */
@ Page
{MSO-page-border-Surround-header: No;
MSO-page-border-Surround-footer: No ;}
@ Page Section1
{Size: 612.0pt 792.0pt;
Margin: 72.0pt 90.0pt 72.0pt 90.0pt;
MSO-header-margin: 361_pt;
MSO-footer-margin: 36366pt;
MSO-paper-Source: 0 ;}
Div. Section1
{Page: Section1 ;}
-->
Original article address:
Http://developer.51cto.com/art/200911/160280.htm