Summary of packaging integration of VS2010 and Crystal Report V13

Thanks to the technical advice provided by Mencius E. System configuration: Windows 7 + VS2010, WinForm + DotNet4 + Crystal Report Here said packaging integration, refers to the production of VS2010 with the installation package, in the installation can incidentally install Crystal Report V13, there are three ways:

first, the use of Crystal Report V13 merge Module example: Crruntime_13_0_1.msm specific steps please refer to the official documentation, the URL is as follows:

http://wiki.sdn.sap.com/wiki/display/BOBJ/Using+Crystal+Reports+for+Visual+Studio+2010+Merge+Modules+ (MSM) +to+ Create+a+setup+project

However, I follow the steps in the article to do, in the installation, will still appear the following tips:

Finally gave up the attempt, ended in failure.

second, the prerequisites for using the deployment project features such as,

prerequisite each item in the component is from the directory: C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages There are subdirectories in this directory crystal. Reports for. NET Framework 4.0, the 32-bit (Crruntime_32bit_13_0_1.msi) and 64-bit (crruntime_64bit_13_0_1) that will be downloaded from the SAP website. MSI) Crystal Report V13 The runtime copy to this directory is ready.

third, the use of custom actions to change the idea: The Crystal Report installation file as a normal file into the installation package, before the end of the installation, using the custom operation function to automatically run the Crystal Report installation files can be. Legacy: I use the second method, in order to reduce development and maintenance work , the company's software is only x86 one version, so the use of Crystal Report is also 32-bit, but the unfortunate is here, installation package installed on the 64-bit operating system, will automatically install the 64-bit Crystal report, resulting in software can not run, but in the production of the installation package, there is no place to set the Crystal Report version. Finally think of a move, the crruntime_64bit_13_0_1.msi Delete, and then Crruntime_32bit_13_0_1.msi copy a name to Crruntime_64bit_13_0_1.msi, This way, both 32-bit and 64-bit operating systems are installed on the 32-bit Crystal report, finally muddle through.
Report:

MDAC 2.81 Bootstrapper Package

http://www.microsoft.com/en-us/download/details.aspx?id=5072

Summary of packaging integration of VS2010 and Crystal Report V13