Dear You dont need to add any additional packages. Just these packages will do every thing you want
The merge modules Crystal Reports 9 are available for download from the Crystal Care Technical Support web site at the following URL:
http://support.crystaldecisions.com/updates/
Once on the web site, search for the merge modules by selecting Crystal Reports from "Select a product," 9 from "Select a product version," and Product update from "Select a file type," and then click Go.
There are potentially four merge modules that need to be included in a setup project to deploy reports.
• reportengine.msm
• crnetruntime.msm
• mapping.msm
• license.msm
The
reportengine.msm merge module is used to install the core files that comprise the Crystal Reports engine. This merge modules is always required for Crystal Reports 9 .NET applications.
The crnetruntime.msm merge module is used to install the Crystal Reports 9 .NET managed components, such as
CrystalDecisions.CrystalReports.Engine.DLL, CrystalDecisions.Web.DLL, and CrystalDecisions.Windows.Forms.DLL.
This merge module is required for all application using any of the managed .NET components.
The mapping.msm merge module is used to install the files required to support displaying geographic maps inside reports. This merge module is only required if geographic mapping is included in your reports.
The
license.msm merge module is used to specify a license keycode in order to determine the scalability of the report engine. This merge module is always required for .NET applications. When license.msm is added to a setup project, it exposes a LicenseKey property that accepts a keycode. The license key is emailed when the product is registered. This key is also available from the VS .NET Help | About… dialog, under the installed products list. The 19-digit license key must be entered into the LicenseKey property for the license.msm merge module.
If the license key is not set for the license.msm merge module, an error will occur when building the project. If the setup is installed on a target computer without specifying the license key for the merge module, various “keycode.dll” errors will occur.
Since Crystal Report for VS .NET is based on the .NET Framework, the framework must also be distributed and/or installed on the target computer. When a setup project is created, usually the framework merge modules will be automatically included.
There are two other merge modules that may need to be included depending on the report(s). If any of the report files are based on ADO.NET dataset objects, the VC_CRT and VC_STL merge modules need to be included in the setup project. These two merge modules are required because the database driver, crdb_adoplus.dll, is dependent on files installed by these merge modules.
Important: When these two merge modules are added, there is a ‘MergeModuleProperties’ property for the file. If you expand that, one of the properties is “Module Retargetable Folder” – this is set to Default. Click on the drop down list to select a different folder from the default. Select the ‘Browse’ option and it will list the folders available on the target machine. A system folder will need to be added before you can set this as the new target folder.
Distributing application with crystal report
Linear Mode
