The R1 2020 Service Pack of Telerik Reporting and Telerik Report Server is now live! We bring important enhancements and bug fixes.
Below are some of the improvements that are part of our brand-new service pack release:
The rendering engine is now forced to skip all pages that do not contain significant content. The latter are considered blank and this includes all pages that only contain items of the following type: Report, Group, any Section, empty SubReport item, Cross-section item, i.e., they do not contain items like TextBox, PicturePox, Table, etc.
You can still control this rendering behavior, so that pages that do not contain significant content get rendered by setting the SkipBlankPages property of the report to False.
All Report Viewers and paged export formats (without RTF-Table mode) conform to this behavior. The viewers show a dedicated message in the report area when it appears that the report has no pages to display.
With each release, we invest a lot of time and effort on our Web-based report designer to make it a fully functional report authoring tool. Now deleting an item from a report with many live items is much faster than before and over 10 bugs were fixed for the Service Pack.
The ASP.NET Core service implementation no longer requires setting the property AllowSynchronousIO to true. Basically, in .NET Core 3+ by default synchronous operations are disallowed. These operations are used to download resources such as images used in the reports. Previously, they needed to be manually allowed by setting the AllowSynchronousIO to True in the container services(Startup.cs) which now is not necessary.
The report viewers' item templates for Visual Studio are now listed in various technologies. This means when you add a new viewer page or window, only the respective item templates according to UI technology and target .NET framework will be shown.
Using asynchronous methods required changing our public API. Please make sure to check the release history about the changes you may need to apply to your applications.
Now the Telerik Report Server provides a way to configure the application's CORS settings. It can be configured during the application startup by the CORS extensions provided by the Microsoft.Owin middleware. The CORS setting can have one of the following states: Enabled, Disabled, Not Set.
For a full list of big fixes and new features, feel free to check out the complete release history. As usual, your feedback is what drives our development plans. Feel more than welcome to reach out in the comments under this post or in our Feedback portal and let us know how we can improve the designer.
Telerik Reporting is a complete, easy-to-use, and powerful .NET embedded reporting tool for web and desktop applications that support: Blazor, ASP.NET Core, ASP.NET MVC, ASP.NET AJAX, HTML5/JS, Angular, React, Vue, WPF, WinForms and UWP. Also available as a part of our Telerik DevCraft bundles, Reporting allows you to create, style, view, and export rich, interactive, and reusable reports to attractively present analytical and any business data. Add reports to any business application through report viewer controls. Export the ready reports in more than 15 formats. Download a FREE trial today.
Neli Todorova was a Technical Support Engineer in the Telerik Reporting division.