The reporting engine calculates the exact physical area necessary for each symbol and report item in the report. The physical size of the items depends on the DPI. When the application using the reporting engine is DPI aware, the items will be calculated based on the real DPI and the report will appear correctly. If the application is *not* DPI aware, the default value is 96dpi, which may generate an unexpected report layout in higher DPI environment. Hence, the application hosting the reporting engine needs to be DPI aware to generate the correct output.
If you prefer not to declare the entire application as DPI aware, you may extract the reporting part in another application declared as DPI aware, and call this application from the main one - e.g. by using Process.Start
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items