After upgrading Telerik.ReportViewer.BlazorNative to version 20.2.26.1007, rebuilding a project targeting .NET 9 or later fails with the following error:

Severity Code Description Project File Line Suppression State
Error (active) The asset 'C:\...\BlazorApp1\Debug\net10.0\compressed\14jp1i84hx-{0}-2x8nbomfaf-2x8nbomfaf.gz' can not be found at any of the searched locations 'C:\Users\<user>\.nuget\packages\telerik.reportviewer.blazornative\20.2.26.1007\staticwebassets\css\reporting-blazor-viewer.css.map' and 'C:\Users\<user>\.nuget\packages\telerik.reportviewer.blazornative\20.2.26.1007\staticwebassets\css\reporting-blazor-viewer.css.map'. BlazorApp1 C:\Program Files\dotnet\sdk\10.0.301\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.Compression.targets 276

-----------------------------------------------------------------------------------

The issue occurs because the NuGet package declares a CSS source map as a static web asset but does not include the corresponding file.

For the available workarounds, refer to the following Knowledge Base article: Missing CSS source map causes build failure in .NET 9 and later with Telerik.ReportViewer.BlazorNative 20.2.26.1007

The data source preview in the web report designer does not show the full shape of the query. It has no horizontal scroll bar to verify the preview data for the entire projection.

Please consider addressing this.

When a Table has a Group PageBreak that splits the Table into more than one page, the items below the table are rendered after the first part of the Table (after the first page break), rather than under the whole table.

The issue occurs in hard pagination: PrintPreview of the viewers, PDF, etc.

The issue is caused by an issue in the SQL DataSource Wizard that doesn't provide the correct Data Provider name. In the wizard on the first page, the Data Provider must be MySql.Data.MySqlClient, but the option is limited only to MySql.Data. Since the engine cannot determine the type of the data provider by that name, it falls back to System.Data.SqlClient and claims that "Port" is not a supported keyword.

I have a CS report that contains a SubReport with InstanceReportSource. I have it in a .NET 10 Classlibrary project.

I tried to edit this report as a coded report in SRD.NET. However, when I saved the report, in the 'designer.cs' file, the value assigned to the ReportSource of the SubReport was set to 'userreport1' that is not instantiated and throws.

I am using the Standalone Report Designer for .NET to open a code-based report from an application that was migrated from .NET Framework. Before the migration, function calls defined in the designer.cs file were preserved and evaluated at runtime as expected. However, after migrating to the code-based reports functionality supported by the Standalone Report Designer for .NET, these function calls are evaluated immediately during the report import process, and the resulting values are then serialized and stored in the report definition.

It would be nice if the function calls were preserved in the imported report, allowing them to be evaluated later at runtime, as their return values may change depending on the execution context.

We have spotted that PInvoke is now marked as deprecated (this applies even to the latest 0.7.124 version). In the description of the PInvoke.User32 NuGet package, it is mentioned that Microsoft.Windows.CsWin32 should be used instead:

Please consider replacing the deprecated package.

I have noticed that the performance of exporting reports has gotten worse in recent releases. After investigating, I found out that this is likely caused by the sheer size of the code in my projects.

To prove this, I created a simple application that renders a report to PDF programmatically. Then, I created 10 000+ dummy classes in the same project, and tried rendering the report again. The performance was noticeably impacted by this change.

Currently, when you set SplitWorksheetOnPageBreak to True, the Excel Sheet name is formed from the DocumentName or ReportName and the number of the page.

It would be very helpful if the report authors can manipulate these names with Expressions.

Currently, the desktop viewers don't allow adding custom headers to their requests to the service.
In HTML5-based web viewers, this is possible through the AjaxPrefilter event.

Currently, when I create a report with the Standalone Designer and localize it, I can preview it only with the language of the machine where I run the designer.

It would be very helpful to have the option to select one of the languages I have set up during localization when previewing.

Currently, if I want to see what the device info settings for an extension like the PDF are, I need to open the documentation - Telerik Reporting Configuring the Output Formats PDF Device Information Settings - Telerik Reporting, then copy the setting that I wish to use in my code.

It would be easier and safer if the device information settings for each format were exposed as a public enum/class. On that note, it would also be easier if the available formats were exposed as well, instead of manually typing them. For example:

public static classTelerikDeviceInfoSetting
{
    public static class PDF
    {
        public const string DOCUMENTTITLE = "DocumentTitle";
        public const string DOCUMENTAUTHOR = "DocumentAuthor";
        public const string DOCUMENTSUBJECT = "DocumentSubject";
        public const string DOCUMENTPRODUCER = "DocumentProducer";
        public const string DOCUMENTCREATOR = "DocumentCreator";
    }

    public static class XLSX
    {
        public const string USENATIVEPAGEHEADER = "UseNativePageHeader";
        public const string USENATIVEPAGEFOOTER = "UseNativePageFooter";
        public const string SHOWGRIDLINES = "ShowGridlines";
    }
}

public static class TelerikRenderingExtension

{

public const string PDF = "PDF";

public const string XLSX = "XLSX";

}

At the moment it's only possible to have your reports in old-fashioned projects.

It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).

When I enable accessibility in my reports, the final PDF document becomes 20+ times bigger than without accessibility. The reports contain large amounts of data and result in 2000+ pages.

I need the images in my reports (usually only one logo) to have alternative text, so the screen readers can describe them. To achieve this, currently I have to enable accessibility for the entire report, hence the huge final documents.

It would be very useful for my scenario to add alternative text to the PictureBox without declaring the entire report as accessible.

The attached sample has a simple table with two row groups, and "header" rows created via "Insert Row -> Outside Group - above".
The groups have "keep together" set.

But despite this, the header rows render at the bottom of one page, with data rows on the following page. This should never happen, I can't think of any case it would be expected (it would be like having "Chapter 2" at the bottom of a page when the text for it starts on the next page). 

I also have a sample with just 1 row group, but with 2 detail rows, and the same thing happens. It only appears to work when there's just 1 row group and 1 detail row.

When generating PDF/UA files, we need to have special objects that are read by an internal system but ignored by screen readers. This cannot be achieved with the existing functionality.

It would be beneficial if we could configure reports so that specific objects inside the generated document are ignored by screen readers. For example, by setting a special value to the AccessibleRole property of a text box.