Hi all,

Just wanted to share our latest improvements to Telerik Reporting for .NET Core. In R1 2019 SP1 we improved the fonts discovery for non-Windows platforms in PDF rendering, so there is no need to explicitly declare the fonts in the configuration file. We have also enhanced the data providers collection, adding support for some of the most used database engines like PostgreSQL, MySQL, SQLite and Oracle.

We will be really glad to hear from you about Telerik Reporting for .NET Core so please share your feedback here, in a support ticket, or in a forum thread.

We are happy to announce that in R1 2019 we're introducing .NET Core support for Telerik Reporting runtime. Report generation works on Windows and Linux platforms for console and ASP.NET Core applications. The product installer now features a fully functional ASP.NET Core example to help you get started.

Most data source components, including ObjectDataSource, are supported. At this point there is no support for Visual Studio Report Designer so the report definitions can be created programmatically or - as we recommend - with our Standalone Report Designer. Тhe .NET Core projects including the ones referencing the full .NET Framework depend upon the VS new project system, that has some limitations about the design time support. Telerik Reporting VS Report Designer uses some components from the .NET Framework that currently are not supported in the new project system. The same components are used by the Windows Forms Report Designer and currently as elaborated in this GitHub thread - support for design time is still work in progress. Once the .NET Core frameworks starts supporting the necessary design time components we will make our best to add the design-time experience to .NET Core report libraries.

For more details please check the related documentation article here: Telerik Reporting - .NET Core support.

We'll be glad to receive any feedback for this major feature.

What we can implemnt additionally is a new item template for ASP.NET Core web app that adds the necessary nuget dependecies along with ReportsController implementation and web page with the HTML5 Report Viewer. With that plan we change the status of the request to Approved.

About the ObjectDataSource you have to add app.config configuration file to the project's root and add the required configuration as elaborated in http://docs.telerik.com/reporting/objectdatasource .  

Up to the report designer. Generally, we don't recommend to add the reports directly in the viewer project. Instead, our suggestion is to create a class library that contains your reports. Then you can reference that class library in applications that view the reports. You can have any number of Windows or Web viewing applications which are re-using the same class library. This solution structure decouples your program logic from the report and its data.

Give it a try and let us know if you experience any difficulties.