This example illustrates how to make the DocumentViewer store its document on the client between postbacks.
When the Document Viewer extension performs a callback to the server (for example, when a page is changed), the report document is restored from the cache. So, it is not necessary to recreate a report document and data is not retrieved from the database. The Document Viewer manages a cached document by using the CacheReportDocument and RestoreReportDocumentFromCache delegates.
To be able to use this approach, it is necessary to move your report data binding code to its DataSourceDemanded event handler.
To learn how to accomplish this task in ASP.NET WebForms applications, see the following code example: How to use the caching functionality of the Document Viewer
Note: No document caching is required when using the newer ASPxWebDocumentViewer control that utilizes the HTML5/JS technology and provides asynchronous building of documents out of the box.
Question Comments
Added By: Felix Zamora at: 7/30/2015 11:25:50 AM
Its a excellent example. But How would the same example with Report Designer?
Added By: Vasily (DevExpress Support) at: 7/31/2015 2:41:05 AMThank you, Felix!
To process your recent post more efficiently, I created a separate ticket on your behalf: T273520: Web Report Designer - How to cache the report document. This ticket is currently in our processing queue. Our team will address it as soon as we have any updates.