Crystal Reports uses merge modules to ensure the correct report components and assemblies are installed with your deployment project.
Each merge module is designed for different deployment scenarios.
Note Adding more merge modules to the deployment project than what is specified in the scenarios may cause deployment problems.
The following table describes the relationship between merge modules and report binding scenarios. You can add the merge module to Web or Windows applications that use report binding scenarios listed on the right column.
Note You must add the mapping merge module to deployment projects that use map objects in the Crystal report files. The mapping merge module can be combined with any of the three merge modules.
| Merge module |
Report binding scenarios |
CrystalReports10_NET_EmbeddedReporting.msm
- Contains CrystalReportViewer controls, Crystal Reports .NET SDK assemblies, RAS SDK assemblies, report processing engine, database and export components.
- Requires a valid keycode.
- Allows a developer to select the database driver.
- Used for Web or Windows applications that do all report processing within those applications.
|
- Binding to a File Directory Path
- Binding to an Embedded Report Class
- Binding to an Embedded Report Class Upcast to ReportDocument
- Binding to a Non-embedded Report Class Loaded into ReportDocument
- Binding to a Cached Embedded Report Class
- Binding to a Non-embedded Report Class Loaded into a Cache Management Utility Class
|
CrystalReports10_NET_RemoteReporting.msm
- Contains CrystalReportViewer controls, Crystal Reports .NET SDK assemblies, and RAS SDK assemblies.
- Does not have Crystal Reports runtime files.
- Used for Web or Windows applications processing reports on an unmanaged RAS server.
- Used for Web or Windows applications that open reports from Crystal Enterprise repository and that process reports on Page Server or managed RAS server.
|
- Binding to ReportSource (Crystal Enterprise 10)
- Binding to Report Application Server (Crystal Reports 10)
- Binding to Crystal Enterprise (Crystal Reports 10)
- Binding to Unmanaged RAS Using ReportDocument.Load() Method (RAS 10)
- Binding to Unmanaged RAS Using ReportDocument.FileName Property (RAS 10)
- Binding to Unmanaged RAS Using ReportClientDocument.Open() Method (RAS 9 and up)
- Binding to Managed RAS Using ReportDocument.Load() Method (RAS within CE 10)
- Binding to Managed RAS Using ReportDocument.FileName Property (RAS within CE 10)
- Binding to Managed RAS Using ReportAppFactory.OpenDocument() Method (RAS within CE 9 and up)
- Binding to InfoObject Cast as Report
|
CrystalReports10_NET_WebServiceReporting.msm
- Contains CrystalReportViewer controls and Crystal Reports .NET SDK assemblies.
- Used by client machines to view reports that are stored and processed on Report Web Services.
|
- Binding to a Report Web Service URL
|
CrystalReports10_maps.msm
- Contains mapping runtime files.
- This merge module is never deployed alone.
- Used when Crystal reports have Map objects.
|
- Applies to any report binding scenario that uses reports with Map objects.
|