Key points for packaging and deploying crystal report. net

Procedure:

1) in the installation project

2) select project --> Add --> file --> open

3) Generally, dependencies are automatically added to "detected dependencies". If not, manually add them to 4)
Crystal_managed2003.msm (if there is a crystal Report)
Dotnetfxredist_x86.msm (. NET must be required)
... (If any other DLL is referenced)

4) manually add the file to be included: Project --> Add --> Merge Module (add your Program File) (including dotnetframework and mdac27)
Located under: C: \ Program Files \ common files \ merge modules \

The specific functions are as follows:
(Managed component MSM processes distribution of all managed components, including windows form viewer, web form viewer, and all crystal decisions namespaces)
* Crystal_managed2003.msm,
Crystal_managed2003_chs.msm,

(For all other files required for running the report, the database accesses the MSM to process the distribution. These include database, export, and chart drivers .)
* Crystal_database_access2003.msm,
Crystal_database_access2003_chs.msm,

(Keycode MSM processes the installation of the crystal decisions key number. Note that the merging module is added; otherwise, the "mergemouduleproperties" attribute is not available)
* Crystal_regwiz2003.msm,

(It is the VC Runtime Library. It is estimated that it is crystal report or some programs involved are written in VC, so we need it !)
Vc_user_crt71_rtl_x86 _ ---. MSM,
Vc_user_stl71_rtl_x86 _ ---. MSM,

5) open solution --> right-click the properties of crystal_regwiz2003.msm, and fill in the "license key" in "mergemouduleproperties: aap5gksjwgde100ds (this is the password of the registration number used to generate the Crystal Report !)

6) generate a solution (or press Ctrl + Shift + B)

So far, the entire distribution program has been completed.