In Development
Last Updated: 21 Sep 2022 14:24 by Yudiel
Scheduled for R3 2022
Dmytro
Created on: 21 Jan 2019 07:18
Type: Feature Request
77
Make Visual Studio designer work with .NET Core (a.k.a. SDK-style) projects

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).

44 comments
Yudiel
Posted on: 21 Sep 2022 14:24

Hello Ivan,

 

Thank you for all this information. Do you have any estimate on when this feature will be released?

 

Thank you,

Yudiel

ADMIN
Ivan Hristov
Posted on: 21 Sep 2022 14:15

Hi Eman,

I'm glad my post helped.

The bidirectional conversion of reports between the Visual Studio Report Designer and Standalone Report Designer is available for years and the process is described in How to import reports created with the VS Report Designer and How to import reports created with Standalone Report Designer. Reports made with Visual Studio can be imported in the new Standalone Report Designer for .NET and we do not plan to change this - quite the opposite, we have plans to improve the import process. In fact, we've always suggested to use the Standalone Report Designer for report authoring, because of its declarative report definitions which are framework-agnostic. True, the Standalone Report Designer by design does not have event handlers and does not support custom code, but in almost all cases these limitations can be mitigated.

So, to confirm - our plans are to preserve the importing logic from and to Visual Studio Report Designer. You will be able to import your type definition reports from a .dll into Standalone Report Designer for .NET, and you'll be able to import them back to Visual Studio Report Designer for .NET, when it's available. Naturally, all the restrictions imposed by the import process will still be applied. As for the process itself - it's handled by the convenient Wizards in both Standalone Report Designer Open File dialog and Visual Studio Import Wizard, and takes just a few clicks to complete, so I'd say it's far from complex.

Regards,

Ivan Hristov

Eman
Posted on: 21 Sep 2022 12:33
Hi Ivan,

Thank you for your detailed explanation; really appreciated.

I have just one concern which is still not very clear for me. If we decide to start using the Standalone Report Designer targeting .NET 6 to create reports for now, when the .NET Core support for the Visual Studio Designer is out, would we be able to use the VS Designer to edit and maintain these already created reports (from the standalone designer)? If there is a transition process, how complex would it be?

Thank you once again,
Eman
ADMIN
Ivan Hristov
Posted on: 21 Sep 2022 11:39

Hi all,

My name is Ivan Hristov – engineering manager in Telerik Reporting. I would like to share with you what is the current state of the Visual Studio Report Designer for .NET Core and why we did not manage to release it as planned. But first, please take a look at the GIF below:

Visual Studio .NET Core designer Work in Progress

This is a Telerik Report Designer running in Visual Studio in a project targeting .NET 6. As you can see, there are lots of things working – design surface with rulers and toolstrip, Properties tool window, complex expandable editors for collection objects, and more. Selecting, moving, and resizing the report items is also implemented. We were convinced we are moving in the right direction until we found out that some of the major architectural decisions we made at an earlier stage, were not fully compatible with the new Visual Studio WinForms designer, resulting in poor design time experience and performance issues.

Naturally, we changed our approach to solve these problems, however the Visual Studio WinForms designer for .NET Core is brand new and while Microsoft had done a great job with it, at this point of time it seems that its capabilities are not yet on par with the full framework designer, especially for the complex integration that Telerik Reporting has with it.

The good news is that the awesome team at Microsoft was already planning to introduce support the integration that we rely on, and we’re currently closely collaborating with them, trying to find a resolution.

However, we did not stop there as we wanted to still be able to allow our clients create reports, using their .NET Core business layer. Therefore, we managed to rebuild the Standalone Report Designer targeting .NET 6. Although it still has some limitations, which we will address in future releases, this approach can be used in the interim to create reports. We also will soon share resources on how this Standalone Report Designer can be used as a workaround to edit existing compiled reports for that people that have urgent need to do that and cannot wait for the Visual Studio Report Designer to come to life.

With this rather long post, I hope I managed to explain what problems we stumbled upon while implementing the Visual Studio .NET Core Report Designer and how we tried to solve them. We understand how important it is to you and we’ll continue working on delivering a fully-featured and reliable Visual Studio report designer. We will make sure to send updates in this thread as we have them.

On behalf of the whole Reporting team, I would like to thank you for your patience and understanding. As always, you are more than welcome to share your thoughts and we’ll be happy to answer.

All best,

Ivan Hristov

Reporting Team

Yudiel
Posted on: 19 Sep 2022 14:58
Same for me. I have been waiting a long time for this update.
Eman
Posted on: 16 Sep 2022 14:19
Any updates on this please? Having the same issue as Adrian.
Adrian
Posted on: 15 Sep 2022 15:17

Hi Milen

What has happened with this?

I did the update and it does not allow me to create and design reports in dotnet 6??

It is still showing in the roadmap for the reporting and the release only states .net 6 as being supported in the standalone designer?

 

 

Adrian

ADMIN
Milen
Posted on: 05 Aug 2022 09:38

Hi Adrian,

Our engineering team members are putting their hearts into this feature and I am confident we will have the core functionality released in mid-September. What will be most probably missing are more or fewer popup editors as each one of these requires explicit wiring and its development time accordingly. You would be able to use the Property grid toolbox instead for most of the functionality.

Regards,
Milen
Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at https://learn.telerik.com/.
Adrian
Posted on: 02 Aug 2022 13:32

Hi Neli

Just wondering if this is still expected as part of the q3 sept 22 release?

 

Regards

 

Ade

ADMIN
Neli
Posted on: 15 Jul 2022 11:24

Hello Ade,

Thank you for sharing your feedback with us.

Here you can find some articles that are related to connecting to Entity DataSource:

Connecting to an Entity Data Model with the EntityDataSource component

- Use Telerik Reporting in .Net Core with Entity Data Model

Regards,
Neli
Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at https://learn.telerik.com/.
Adrian
Posted on: 08 Jul 2022 10:03


 Hi Milen

 

I think the issue is that the workaround and the code example "VS Designer Core" needs to include an example of the report consuming data in the code behind (using entity framework for example) in both the designer supported class library (dot net 4.8) and the net 6 class library.

eg: passing in a list of data through a public method in the report's code behind and binding it to a table, or the report itself accessing the data itself.

 

Ade

ADMIN
Milen
Posted on: 14 Jun 2022 12:49

Hi Aldo,

I agree that the VS designer coverage of .NET Core/5/6/7 projects is fundamental and gradually became a must along with the high .NET adoption. This is why we started R&D on this task back in the R2 2021 release cycle (~14 months ago) and committed to providing updates on the progress.

The technical reality is that the designer has a huge code base which we need to adapt to the new visual designer architecture that Microsoft introduced. We're continuing to refactor our design-time code, splitting it to fit that client-server architecture. This part of the process is the foundation of the design-time support and cannot be partially released. The main part of our development capacity is currently dedicated to this feature, which makes me believe we will be able to have it released in R3 2022. Even if not 100% functional, we will make sure to have the core functionality in place, while, for example, some specific editors might still not be available.

Meantime, we can try helping with the difficulties you experience implementing the proposed workaround with a parallel .NET Framework library. Others could have such as well. Let's help the community.

Our ultimate goal is to have the same seamless experience when you open your .NET Framework reports in the new .NET Core Visual Studio Designer, so no "porting" or "converting" would be necessary.

Thank you for understanding.

Milen

Aldo
Posted on: 13 Jun 2022 08:42

Hi, is it possible to have some updated information about the estimated date for this FUNDAMENTAL feature ?

We cannot wait for it anymore, we have project that need to port a lot of report and actual workaround can't be a way.

If we have to do a lot of work to maintain those reports, we prefer to move to another product, because we're near to NET 7 release and is unacceptable that the report designer still does not work with NET Core/5/6/7.

Please give us a sure and reliable answer.

Regards
Aldo

ADMIN
Milen
Posted on: 28 Apr 2022 09:14

All,

Thank you for expressing your concerns about that feature. I completely understand your pain and want that implemented no less than you all. Still, I will have to announce that it is still not ready for release despite our efforts. Stay tuned to this thread as I will announce here our progress. We are targeting now the R3 release due in mid-September. Thank you for being our loyal customers. 

Regards,
Milen
Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at https://learn.telerik.com/.
Jon
Posted on: 21 Apr 2022 10:44

I was also wondering

We have also projekts that we want update and waiting for update of reporting

 

best regards

Murat

Adrian
Posted on: 21 Apr 2022 10:41

Hi 

 

I was wondering if this will make the release for next month?

The work around does not quite work for how a lot of the reports have been created in some of the projects.

I have a number of projects looking to upgrade to dotnet 6 as part of their next major upgrades and wanted to make sure this is in place first.

 

Many Thanks

 

Ade

ADMIN
Milen
Posted on: 06 Jan 2022 12:15

Hello Deepak and all,

It is the last thing I would like to announce, but the designer will not make it in the January release. We have solid development on that feature but we did not manage to implement all the editors and design surface functionality in the new VS designer paradigm. It just appeared the scope and complexity of the implementation exceeded our expectations. That said, it is still not ready to serve you, our users. I am rescheduling it for the mid-May release which I sincerely believe is an achievable milestone. Meantime please refer to this workaround to be able to edit CS reports and use them in your .NET Core 3+/.NET 5/.NET 5 projects. Sorry for the inconvenience.

Regarding the particular question, Deepak, yes, the designer targets both VS versions 2019 and 2022.

Have a great year all of you,


Milen
Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at https://learn.telerik.com/.
Deepak
Posted on: 04 Jan 2022 14:08

Hello,

Glad to see that this feature is scheduled for R1 2022. 

Just 1 follow-up question.  Will the new Report Designer for .NET 5/6 work with Visual Studio 2019 or 2022 or both?

Deepak.

Kori
Posted on: 17 Nov 2021 14:35
https://devblogs.microsoft.com/dotnet/whats-new-in-windows-forms-in-net-6-0/
Philbert
Posted on: 02 Nov 2021 11:19
Also waiting for this as well
Kori
Posted on: 25 Oct 2021 13:40

@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].

Deepak
Posted on: 23 Oct 2021 00:27

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.

 

Kori
Posted on: 22 Oct 2021 15:24

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.

Dmytro
Posted on: 22 Oct 2021 11:35
Yeah, this has been open for almost 3 years now. .NET Core come and gone, .NET 5 is in use, .NET 6 is released in 2 weeks. And still we have to do all sorts of jumps through the hoops around Telerik Report Designer ...
Adrian
Posted on: 22 Oct 2021 10:59

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

Deepak
Posted on: 30 Mar 2021 15:40

Thanks for the clarification!  Really looking forward to it.

ADMIN
Milen
Posted on: 30 Mar 2021 05:42

Hello all,

It is our process for an item to go through Under Review -> Unplanned -> Planned. Apologies for the misunderstanding. Having in mind the technology trend and the votes for this feature it is one that we will put serious effort into to release in R3 2021.

Regards,
Milen
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Andrea
Posted on: 29 Mar 2021 17:47

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

Deepak
Posted on: 29 Mar 2021 16:31

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

Kori
Posted on: 26 Mar 2021 16:42
What? This is "unplanned" now? Do you know the terrible workaround that's necessary for this currently??
Deepak
Posted on: 03 Nov 2020 14:14

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

Thank you

ADMIN
Todor
Posted on: 03 Nov 2020 10:35

Hello all,

Our plans do include it for 2021. We will post an update once we have a more granular estimate.

Regards,
Todor
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Jon
Posted on: 29 Oct 2020 06:44
I Hope this feature comming soon
Dmytro
Posted on: 28 Oct 2020 17:19
Well, we need someone from the team to tell us if and when they are planning to work on this issue. The only way for us to make it happen faster is to upvote the feature request. So, guys, please do that :)
Kori
Posted on: 28 Oct 2020 15:53

@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.

Deepak
Posted on: 28 Oct 2020 15:38

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.

Kori
Posted on: 27 Oct 2020 15:04
Is this coming? Anything?
Deepak
Posted on: 26 Jun 2020 19:03
I agree that the main goal should be to get rid of .NET Framework.  Even .NET Standard will be deprecated along with it.  If this can be achieved with .NET 5, then I can wait :-).
Dmytro
Posted on: 26 Jun 2020 19:00
Hi Deepak, we also do something along those lines. However, the main point was to get rid of .NET Framework altogether from our product. At this moment, VS Report Designer is the only reason we have to keep that around. For now it looks like, we will not have this feature until .NET 5 is out + whatever time Progress needs to adjust their stuff. So, somewhere February 2021 would be a fair guess. I'm an optimist :D
Deepak
Posted on: 26 Jun 2020 17:54

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:
<ItemGroup>
<Compile Include="..\ABC.Reports.Design\**\*.cs" />
</ItemGroup>
<ItemGroup>
<EmbeddedResource Include="..\ABC.Reports.Design\**\*.resx" />
</ItemGroup>
  • 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.

 

ADMIN
Ivan Hristov
Posted on: 01 Oct 2019 08:55

We are keeping a close eye to the efforts of the .NET team that works on the Windows Forms designer on .NET Core. Yesterday they've introduced a preview version of the designer - it looks promising, but there are still lots of missing features. For example, containers, resources and component tray are not yet supported, and they are mandatory for our reports designer. We are sure that the subsequent versions of .NET Core Windows Forms designer will add the missing features, but its current state is just not fit for our needs. Please rest assured that we understand how important this designer is for our clients and as long as it is released with all the necessary components, we will do our best to include it in the next version of Telerik Reporting.

Regards,
Ivan Hristov
Progress Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Dmytro
Posted on: 24 Sep 2019 09:01
Is there any update on this issue? .NET Core 3.0 is already out, but we still cannot switch because our reports require .NET Framework 4.7.2... This does not make any sense, to be honest. I know, I know, we can containerize report projects and so on. But that is too much work just to make Telerik Designer happy.
Kori
Posted on: 25 Jun 2019 15:16
Tracking this item, where they are working on ComponentDesigner compat https://github.com/dotnet/winforms/issues/989
ADMIN
Todor
Posted on: 25 Jan 2019 16:21
Hello Dmytro,

Currently, the .NET Core frameworks do not support the design time components we need for our Visual Studio Report Designer. Without these components we cannot provide a quality design-time experience. We believe that VS team will gradually fill the gaps between the .NET Framework and the .NET Core, publishing more and more designer classes. As soon as the necessary components become available we will make sure our designer is working when hosted in .NET Core and  .NET Standard projects.

Regards,
Todor
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items