As soon as I reference a .NET 10 assembly containing models, there is a null reference exception that does not appear in EventViewer or Fusion logging at the opening of the Standalone Report Designer for .NET.

Here is a link to a muted video demonstrating how adding assembly references using the UI successfully adds the custom assembly to the designer, as well as the bug when removing the assembly version.

Hello Team Support,

I work with the ReportViewer in WPF. I modified the description of some format in my App.config.

When I export my report, if the description is too long, it does not fit the message window anymore.

Here is a screenshot of my issue:

Thank you in advance.

Best regards,

Jonas

Some of the Web Report Designer pop-up messages are not localizable. For example, the message about trying to access a report that does not exist on the server:

Related to:

https://feedback.telerik.com/reporting/1635210-attempt-by-security-transparent-method-telerik-reporting-openxmlrendering-spreadsheet-workbook-ctor-to-access-security-critical-method

Also affects Telerik.Reporting.Processing and Configuration: Attempt by security transparent method 'Telerik.Reporting.Processing.AssemblyRefManager.LoadAssembliesCore()' to access security critical method 'Telerik.Reporting.Configuration.ReportingConfiguration.get_Current()' failed.

Some special characters, such as "🍁", break reports that are rendered with the Skia graphics engine in a Linux environment.

When the Gdi graphics engine is used on Linux, the reports are generated successfully. However, the Gdi graphics engine cannot be used on Linux with projects that target .NET 7 and later.

Currently, the GetDesignerResource endpoint of the Web Report Designer service is case-insensitive, which can lead to issues if the URL is made lowercase at some point, such as by a URL rewrite rule, or similar scenarios.

For example, the following reference to the Web Report Designer script will load return the file:

<script src="api/reportdesigner/designerresources/js/webReportDesigner"></script>

But if lowercase is used, for example, like this:

<script src="api/reportdesigner/designerresources/js/webreportdesigner"></script>

The request will return a 404(Not Found) response.

Using Blazor native reporting component.  Our underlying email sending service requires that Subject is not blank, however the UI does not validate the Subject field.

Need to be able to validate that Subject is not blank when user attempts to submit email form.

We are experiencing issues with Telerik Reporting related to RTL text (culture 'ar-JO') rendering, as outlined below:

• Text wrapping is not working correctly within the HTML5 Report Viewer. The text seems to overflow the TextBox.
• When exporting to PDF, the text exceeds its boundaries, does not wrap as expected, and in some cases is cut off.

I'm getting an error in Telerik Report Designer (Data Explorer): "Member x on type String not found"

The version is: 19.3.25.1119

Steps to Reproduce:

• Open SRD.NET.
• Configure the Assembly References through the SRD.NET UI to include a DLL.
• Open an existing report file.
• Observation: The Data Explorer tool window is populated correctly, showing all fields and methods as expected.
• Close Telerik Report Designer.
• Re-open Telerik Report Designer.
• Verify that the Assembly References are still correctly configured (they are).
• Open the same report file.
• The Data Explorer is not populated. Instead, it throws an error:

When my application runs in full trust permissions set, the following error is thrown if I have used the Telerik.Reporting.OpenXmlRendering NuGet package and try exporting to any of the OpenXML formats :

ERROR: Attempt by security transparent method 'Telerik.Reporting.OpenXmlRendering.Spreadsheet.Workbook..ctor()' to access security critical method 'DocumentFormat.OpenXml.Packaging.SpreadsheetDocument.Create(System.IO.Stream, DocumentFormat.OpenXml.SpreadsheetDocumentType)' failed.

I am using the obsolete `Telerik.Reporting.Chart` type for a chart in a report. When I attempt to preview the report, an error is thrown:

The type "Telerik.Reporting.Chart" contained in assembly "Telerik.Reporting, Version=19.2.25.1001, Culture=neutral, PublicKeyToken=a9d7983dfcc261be" cannot be loaded.
To help improve the application's security, the reporting engine prevents loading types that are not essentially needed or listed as trusted by the user. If you consider particular types or assemblies as trusted include them in the corresponding TypeReferences or AssemblyReferences element of the 'Telerik.Reporting' configuration section in the application's configuration file.

The PDF with enabled Accessibility looks fine in the Adobe PDF reader.

However, when I check it with the PAC tool, it shows in the logical structure the Detail section first, then the Page Header, and then the Page Footer.

When using screen reader applications like JAWS or Narrator, those tools read accessible reporting PDFs in an incorrect order. For example, if I have two items in the report, the reader will read the second item first.

Additionally, images whose AccessibleDescription I have set may be read multiple times..

I had an issue with watermarks being present in the generated PDF despite the license validation passing. In the trace log, I was seeing this:

x.x.x.x.exe Information: 0 : *** ReportProcessor.ProcessReport STARTED ***
x.x.x.x.exe Information: 0 : SQLite x64: v3.50.4
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : *** ProcessReport #0 "Invoice" STARTED ***
x.x.x.x.exe Information: 0 : *** ProcessReport #0 "Invoice" DONE in 00:00:00.6363067 ***
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : *** ReportProcessor.ProcessReport DONE in 00:00:00.7891276 ***
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : License check for assembly Telerik.Reporting, Version=19.3.25.1119, Culture=neutral, PublicKeyToken=a9d7983dfcc261be: True
x.x.x.x.exe Information: 0 : 
x.x.x.x.exe Information: 0 : *** Render Report #0 "Invoice" STARTED ***
x.x.x.x.exe Information: 0 : ReportName: Invoice; DocumentName: Invoice; Extension: PDF
x.x.x.x.exe Information: 0 : DeviceInfo Contents
x.x.x.x.exe Information: 0 : ===================
x.x.x.x.exe Information: 0 : ChangingPermissionType: ""
x.x.x.x.exe Information: 0 : ComplianceLevel: "None"
x.x.x.x.exe Information: 0 : CopyingPermissionType: ""
x.x.x.x.exe Information: 0 : DocumentAuthor: ""
x.x.x.x.exe Information: 0 : DocumentCreator: ""
x.x.x.x.exe Information: 0 : DocumentKeywords: ""
x.x.x.x.exe Information: 0 : DocumentNaturalLanguage: ""
x.x.x.x.exe Information: 0 : DocumentProducer: ""
x.x.x.x.exe Information: 0 : DocumentSubject: ""
x.x.x.x.exe Information: 0 : DocumentTitle: ""
x.x.x.x.exe Information: 0 : EnableAccessibility: "False"
x.x.x.x.exe Information: 0 : EndPage: "0"
x.x.x.x.exe Information: 0 : FontEmbedding: "None"
x.x.x.x.exe Information: 0 : ForceLicenseWatermark: "True"

The issue turned out to be due to caching, but the output puzzled me while I was debugging this. Turned out `ForceLicenseWatermark` is always true (the misleading part), but only has an effect when the license validation fails.

After dragging a report viewer control from the Visual Studio toolbox to the surface of a Windows Form, the viewer is added to the component tray but it is not added to the Controls collection of the form. Thus, the viewer is not displayed when running the application.

Also, some properties of the report viewer, such as the ReportSource property, are not serialized properly after being modified through the Visual Studio properties window.

Currently, one can work around these issues by manually editing the InitializeComponent component method of the form's .Designer.cs file.

If we initialise the control in "FIT_PAGE_WIDTH" mode it essentially renders as expected but zooming in can actually then cause it to zoom *out*.

Reproducible in the `CSharp.NetFramework.Html5IntegrationDemo` example project as well, once you set the `scaleMode` property to "In FIT_PAGE_WIDTH".