@Deepak I think that's simply because there's no need to release new versions now that the APIs are sorted out and all the bad juju was refactored.

".NET 5 and all future versions will continue to support .NET Standard 2.1 and earlier" from here so that'll work long enough for Telerik to get their act together [hopefully].

We use exactly the same approach that Kori described.  It works.  However, our common code is limited to .NET Standard which prevents us from using any of the newer C# features that are specific to .NET 5 or later only.  .NET Standard is now around only for backward compatibility purposes.  It has no future.  So the sooner we get the .NET Reports Designer, the sooner we can get rid of .NET Framework and .NET Standard from our Visual Studio solutions.

This is the best workaround we personally employ:

• Create a .NET 4.8 project called (projectname).Reports.Core
• Add nuget references to Telerik.Reporting, Svg, etc
• Change the default namespace to (projectname).Reports
• Add a report
• Verify the report designer shows correctly, add _anything_ to the report
• Create a .NET Core/.NET 5/.NET 6 project called (projectname).Reports
• Add the reports generated in the .NET 4.8 project as "links" to the NetCore/5/6 project
• Add the same .net references (Telerik.Reporting, Svg, etc)
• Use the viewer, reference the report in (projectname).Reports
• When editing the reports, open the reports in the .NET 4.8 project. The designer works correctly in this context.

Pros:

• You can get work done.

Cons:

• Depending on how your project is setup, you won't be able to reference your common code unless it's NetStandard.

TLDR; It's like being in the wild west of reporting solutions.

Any updates on this being released in Q1 2022?

I have a number of projects that we are starting next year that would benefit from this.

Adrian

Thanks for the clarification!  Really looking forward to it.

Hello, same situation, I'm porting to NET5 a big project with 50 complex reports that use existing entity framework api data layer. Thank you. 

Andrea

Hello,

We need a way to edit Telerik Reports that directly save as C# files.  If the Visual Studio designer for .NET 5.0 Projects is now "Unplanned", then may we know what's the alternative in the future?  Using .NET Framework projects is not an option.

Thanks.

Deepak Gupta

Todor, that sounds great!  I'll keep an eye out for more information.

Thank you

@Deepak

That's where we're stuck as well. All of our reports are heavily customized and just defining them in the standalone designer isn't possible for us because of that.

Hello,

Just to give some background.  We have over 100 Reports created using the Visual Studio Designer which directly creates C# files for the Reports that integrate nicely with the rest of our projects.  For performance reasons, the Reports use ObjectDataSource that directly refer to our Business Layer classes and methods that uses .NET Standard 2.0.  However, looks like .NET Standard 2.0 is going to be set in stone so that it's compatible with .NET Framework and .NET Core.

Ideally, we would like to convert all our projects to pure .NET Core 5.0+ and remove all dependencies to .NET Standard 2.0 and .NET Framework 4.8.  However, without the updated Visual Studio Designer, we are unable to do that.

Switching to the Windows Desktop or the Web Designer isn't an option for us, is it?  I believe those Designers save the Report Definitions only as XML and we already have over a 100 reports that are pure C#.  Is it possible to convert the C# files to XML and then edit them in the Windows Desktop or Web Designers?

Regards.

Deepak.

Here's what I've done as a workaround.

• Created a Visual Studio solution with the Business Layer as .NET Standard and the Web as .NET Core.
• Added a .NET Framework project for Reports (called it ABC.Reports.Design) which has a reference to the Business Layer.  This is where we use the Reports Designer.
• Added a .NET Core class library project for the .NET Core Reports (called it ABC.Reports) that reference the files in the Design project as follows:
  

• Add a reference to ABC.Reports project within the Web project.

This allows us to then use Visual Studio for the Reports designer and then deploy the .NET Core web project with references to the .NET Core Reports and .NET Standard Business Layer.