An object that acts as a mediator between a report and a Web Document Viewer.
NuGet Package: DevExpress.Web.Reporting.Common
public class CachedReportSourceWeb : CachedReportSourceBase
Public Class CachedReportSourceWeb Inherits CachedReportSourceBase
Use the CachedReportSourceWeb object to display a report in a Document Viewer. This object creates a report document and caches each generated page to a storage. Only pages displayed in a Document Viewer are stored in memory.
Pass a target report as a parameter to the CachedReportSourceWeb object’s constructor.
using DevExpress.XtraReports.Web; using DevExpress.XtraPrinting.Caching; //... var cachedReportSource = new CachedReportSourceWeb(new XtraReport1());
A CachedReportSourceWeb object uses a MemoryDocumentStorage storage to cache a generated document. This storage stores a document in memory in a compact way. Use the UseFileExportedDocumentStorage (.NET Framework) / UseFileDocumentStorage (.NET Core) method to store the report documents in the File Document Storage instead. You can also use the DbDocumentStorage storage or implement a custom one. Register your IDocumentStorageProvider to manage document storage.
Display Large Reports
Use the OpenReport(String) (Web Forms)) / Bind(String) (MVC) / Bind(String) (ASP.NET Core MVC) method to bind the Document Viewer to a report by the unique report name. Implement the ICachedReportSourceWebResolver interface to associate a report’s unique name with the CachedReportSourceWeb object that owns the report. A Document Viewer uses the ICachedReportSourceWebResolver object to find an appropriate CachedReportSourceWeb object by a report’s unique name and requests the found object to generate a report document, when required.
You can also use the OpenReport(CachedReportSourceWeb) (Web Forms) / Bind(CachedReportSourceWeb) (MVC) method to bind a Document Viewer directly to the CachedReportSourceWeb object that owns the report. The report’s interactive features are only available to users until the application pool is recycled. The document needs to be regenerated to make interactive features available. However, after the application pool is recycled, the document cannot be regenerated because the initial report cannot be found.
Merge Large Reports
See the following topic for more information on how to merge reports: Merge Reports in Web Applications.
The CachedReportSourceWeb component cannot be associated with reports that include a PrintableComponentContainer.
When you use the CachedReportSourceWeb component to generate a report document, the PrintOnPage event is raised each time a page with the current control is created. In this connection, the total number of pages is unknown at the moment the event fires and you cannot use the PageCount property in the event handler.
RollPaper mode is not supported.
When you create a report document, the CachedReportSourceWeb component generates data that is necessary to perform single-file export. If you do not plan to export the document in single-file mode, disable the AllowSingleFileExport option to release memory.