Progress® Telerik® Reporting R3 2017

Windows Forms Application

The Windows Forms Report Viewer is designed to render Telerik Reports within Windows Forms projects.

The toolbar on the Windows Forms Report Viewer provides basic functionality for interacting with the currently-loaded report:

  • Navigate back in history

  • Navigate forward in history

  • Stop loading (useful when a large report is taking a long time to load)

  • Refresh

  • Go to first page

  • Go to previous page

  • Go to a specific page

  • Total number of pages

  • Go to next page

  • Go to last page

  • Page Setup (set paper kind, orientation, margins)

  • Print Preview: switches between Logical and Physical page renderer. See Rendering and Paging for more info.

  • Print

  • Export: see Rendering Extensions for available export formats.

  • Zoom level

  • Show/Hide parameters area

  • Show/Hide document map

Note Note

.NET Framework Client Profile is not supported.

How it works

The Windows Forms ReportViewer control is a composite of standard Windows Forms controls.

Note Note

The Windows Forms ReportViewer control's toolbar is immutable. To build custom UI for the toolbar and work with the rendered report in the viewer, you can use the Windows Forms ReportViewer.

The purpose of the Windows Forms ReportViewer control is to display Telerik Reports and allow the user to interact with them. Reports are processed and rendered on the client machine. The report in the viewer is rendered through Telerik Reporting IMAGE rendering mechanism based on the Design Considerations for Image Rendering.

Declaring the application as DPI-aware

When using Windows Forms ReportViewer on a machine with Windows Vista and later operating system and DPI scale factor higher than 96, the form content (labels, buttons, rendered report image, etc. ) might be rendered fuzzy, pixelated and with other visual artefacts. This is because the application in which you are using the Windows Forms Report Viewer is not declared as DPI aware. The recommended approach for declaring an application as DPI aware is adding a dpiAware element to its application manifest, as shown below:

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" >
  <asmv3:application>
    <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
      <dpiAware>True</dpiAware>
    </asmv3:windowsSettings>
  </asmv3:application>
</assembly>

You can read more about writing DPI-aware desktop applications here.

See Also