Report Files

Report files (.rpt) need to be distributed when a .NET application is deployed. You can choose to either compile the report files into the application, or distribute the report files separately from the application.

Embedded Report Files

Embedded report files are files that are compiled into the application. With embedded report files, you can distribute and deploy your application without having to distribute report files separately. When reports are added to a .NET Web or Windows application, they are added by default as an embedded resource for the application. This means that the report will be compiled into the assembly's manifest and will not be loaded from a separate report file (.RPT).

Non-Embedded Report Files

Non-embedded report files are report files that not compiled into an application's assembly and are distributed separately from the application. The advantage of keeping reports outside of the assembly is that reports can be modified and redeployed without having to recompile and redeploy the entire application. The disadvantage is that strongly-typed report objects cannot be used in the application and report files must be distributed separately from the application.

To make a report file non-embeddable

1. After adding a report to a project, highlight the report in the Solution Explorer.
2. From the Properties Window change the Build Action property from Embedded Resource to None.
3. Manually add the report file to the Setup project.

   See Deploying Web or Web Service Applications or Deploying Windows Applications for information on how to create a Setup project.

See Also

Crystal Reports Merge Modules