I have replied to the support ticket you opened on the topic. I will include the relevant part of my answer also here :
rendering is an extra functionality that requires Telerik.Reporting.XpsRendering.dll
file that should be added manually to the project, e.g. our Visual Studio item templates do not add it automatically. The Reporting engine, when called, checks for the available external resources that are necessary for all the supported rendering formats. If an assembly that is required for any of the formats (e.g. Telerik.Reporting.XpsRendering.dll
) is missing, the engine will throw a first chance exception (i.e. passed to the debugger but not passed back to the application), which will be logged just to notify that the assembly is missing. This error will not distort in any way the workflow for the other renderings. Hence, PDF rendering does not depend on Telerik.Reporting.XpsRendering.dll
file and the absence of this assembly cannot interfere with PDF rendering. In other words, the two problems are not related.
rendering logic is part of our main Telerik.Reporting
assembly and does not require any additional assemblies, i.e. it is enabled by default with the installation of the product. PDF format is based on the IMAGE format - check PDF Rendering
. Note that some Azure plans have restrictions related to the GDI+ that we use in IMAGE rendering - check GDI+ error or OutOfMemoryException on exporting or printing Telerik report from Azure WebSites
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