Hi Milen

Ok, Will R1 be here in Q1/2019? (It is my deadline to implement reporting on the server side, otherwise I need to make a [temporarily] dirty hack and move the file generation to the windows client...) Probably I have to do that anyway, since V1 of this feature may not yet be production ready....

Hi Ivan,

Thanks for that feedback. Interesting! libgdiplus is part of MONO but I could not find it in my runtime container. Looks like it is not part of what MS redistributes in its runtime docker image. Try to research a bit more and then change my docker file to get this thing installed in my runtime containers and then give it a try.

Just one question: Is this a supported feature? As a customer can I create a ticket for telerik reports if I have a question regarding this on LINUX?

Just as an addon to my vote:

We run all our services in docker and .netcore 2.1 or higher, there will be NO windows services at all in the very near future. We are currently using Telerik reports. One of your competitors (devexpress) will soon support .NETCore. See announcement https://community.devexpress.com/blogs/reporting/archive/2018/04/26/reporting-net-core-support-ctp-v18-1.aspx.

I would be happy, if Telerik could do the migration too and get rid of the GDI stuff which is Windows propriatary. It would save me some work to port report templates etc.!

Status "In Development" is a very good news.

Thank you Telerik !

Thank you for changing the status to "In Development".

Also, Microsoft releases yesterday 2018-11-04, the .Net Core 2.2 and .Net Core 3.0 Preview.

#Lubica

And that is recommended, to fully support cross-platform.

Also, they start dropping support the Full framework, check any security updates and new features, it will be applied to NetCore without NETFW.

Microsoft drops support for full framework for ASP.NET Core 3.0

ASP.NET Core 3.0 will only run on .NET Core 

We need .net core reporting 

The issue you provide the link for was closed 9 months ago, with the release of WCP "Windows Compatibility Pack".
While the "System.Drawing.Common" released 1 month ago.
And it sits on top of native libraries "libc6-dev" and "libgdiplus" for linux

Don't know about that, it looks a bit ugly: https://github.com/dotnet/corefx/issues/20325

First, I hope we can focus and append all similar requests into one.

Second, I think now Telerik could use the "System.Drawing.Common" Version 4.5.1, It now supports .NETCoreApp 2.0
Check: https://www.nuget.org/packages/System.Drawing.Common

Also, check "Scott Hanselman" blog https://www.hanselman.com/blog/HowDoYouUseSystemDrawingInNETCore.aspx

I hope they can do it, even before the .NET Core 3.0

Can I chime in here to add some nuance to this issue.

The steps to .NET Core Telerik REST API support are as follows:
1) no support (net 4.6.x required for REST API) - CURRENT SITUATION
2) net core 2.x support for REST API, linux and OsX throw PlatformNotSupportedException
3) net core 2.x support over all platforms

To illustrate the impact of these stages, I built my application using net core 2.1, but then had to convert it all to net 4.6.2 to make it work with the REST API. This was a major problem.
Telerik has been suggesting that the front end reporting tools can use the HTML5 viewer in native net core, then host the REST API in a separate net 4.6.x application. This might work for a corporate LAN where security is all taken care of in the networking configuration, but for a public facing website where security requires forms authentication to log into resources, the complexity to add authentication to the API, which is definitely necessary to secure the data, will be prohibitively difficult to set up and co-ordinate since it requires not only two different security setups, but co-ordinated login across both. This is scenario 1) above.
Telerik can claim that this is .NET Standard, but in fact if this were the case it should run on net Core 2.x as well. In fact, this is a .NET classic only solution.

If Telerik supported scenario 2), which would not be at all difficult to implement since it would still only run on windows, then a native net core 2.x application could run the REST API, but only when hosted on Windows. Frankly, hosting net core on Windows is a fairly minor imposition compared to having to port a whole project back to net core 4.6.x, which can then only run on windows, anyway.

Scenario 3) is understandably very complex to implement. It would not surprise me if this took years to implement, and a very significant expenditure of resources by Telerik. In fact, I'm not even convinced it would be worth Telerik's while to do, as it would require the parallel support of Linux, OSX and windows GDI libraries. This would rely on .Net core support of those libraries, which is currently very fragmented and shows no signs of resolving in less than a several-year timeframe. We can be confident that Telerik's use of these parallet GDI libraries would flush out a goodly number of bugs along the way, and that fixes for these bugs would not be under Telerik's control.

Anyway, as a summary to the above I would call on Telerik to move to scenario 2) above ASAP. I do not believe it would be hard to do, and the benefits would be significant.
Scenario 3) would be far more challenging, and I would call on Telerik to undertake a sober evaluation before attempting any work towards it. Because any solution would necessarily depend on the Net Core porting efforts of the drawing libraries, Telerik's effort would have to proceed in lockstep with that project.

We are in desperate need for this in order to implement an API, do you have an estimated release as to when we can have this support?

I see this has request has been "Approved", can you give us any indication which release it may be in as we are looking at porting our software over to .net core 2.1 (2.2)

Please add

Much needed, please add.

Please add

Please add

Since all of our new applications are targeting .NET core and running on linux, we are considering to NOT use the Telerik reporting engine anymore.

.NET Core reached version 2.1 an in my point of view is stable enough to rely on for enterprise grade application.

Telerik should make public statements on his plan for Reporting on .Net Core and eventually release a roadmap on this.

As the lack of information we are actively looking for competitors product (some of them has already their product on public beta/preview).

We are currently running Telerik reporting on .Net Framework 6.2.  Most of our new applications are using DotNet Core.  Our goal is to move all application to running on DotNet Core and Docker containers under Linux.  We really need Telerik Reporting to run on DotNet Core in a Linux environment.

Please add it.

It is critical to have the .net core full support

Yes please add full native support for net core

We also need this feature for our .Net Core 2.0 project. 
Thanks

Please add me to the list of folks that could really use this as well. Thanks.

I understand that Telerik.Reporting uses GDI+ that is available only on windows. But there are other cross platform dotnetcore libraries that can "draw stuff". Changing to some of those might be a double gain for Telerik, because GDI+ is generally not recommended to run on server anyway.

I am glad you have this feature request already registered. I am adding my vote to support net core. Technically we need to be able to use Telerik.Reporting.dll in a library that targets <TargetFramework>netstandard2.0</TargetFramework> so that we could run it as AzureFunctions v2.0 or even host it on a Linux instance of dotnetcore in Azure.

I am so disappointed to know that Telerik reporting is not supporting full .net core, it will be a plus it have it ASAP

Please we need it for net core

Even if this only starts out in the ASP.NET Core capacity, using HTML5 for the viewer and having a ASP.NET Core 2.1 REST service for the report management/generation, this would be far better than having zero .NET Core native support. Obviously NetStandard is were the library should be headed.

Heck just start a brand new product for ASP.NET Core reporting... don't  even worry about a full refactor of the old report engine.

I need this too.

I need this feature 

Desperately need this tool for my .Net Core 2.0 project. Thanks

My vote goes for this feature too, because, as someone mentioned, we are going to deploy the app to linux containers.

I need this too.

I require this as well. thank you.

This would be huge for us as it would allow us to create thousands of reports and statements in minutes instead of lots and lots of hours.

Please add this. Like others, we also would really like to be able to run the report engine on Amazon Lambdas, or a the very least, on Linux instances.

I understand GDI+ is the issue, but System.Drawing library is now supported in .NET Standard 2.0, as of System.Drawing.Common 4.5.0-preview1 . See https://www.nuget.org/packages/System.Drawing.Common . There is also a lengthy discussion about the topic here. https://github.com/dotnet/corefx/issues/20325 . 

We would also like this feature, if possible. We would like to host on Linux containers but we also need Telerik Reporting features embedded in the app.

For smaller hosted projects where it is easier to have the reporting in the the same project.
I vote for this also...

This is a 'must have' requirement to be able to host the report generation service on hosts other than Windows with the full .NET Framework. 

I realise that the report generation relies on the GDI functions and will take some considerable effort to port to .NET Core and so it may be sometime. However, as Samuel mentioned above, a timescale would be good if you can provide it.

I'd like to integrate Telerik Reporting into my existing CORE 2.0 Project to reuse existing business logic and interfaces.
We use ASP.NET Boilerplate/ZERO Components and definitely want to avoid backing down/"downgrade" since it is too late to reuse other ABP templates for our project.

You have my sincere vote to introduce full CORE 2.0 Support.

Some estimation about whether or not and when you think this feature will be introduced would be appreciated.

Thank you.

me too facing the same issue. Now unable to host on linux bcos of full .net dependency. Kindly provide the solution for the same

I have exact the same need.  Our main project Asp.net Core 2.0 Mvc project targets .net Core 2.0 since it must run on a Linux server and we would like to add reporting that does not depends on the Windows O.S. 
So it has my vote!