Best solution for migrating legacy reports to .net core ?

3 posts, 0 answers
  1. Frédéric
    Frédéric avatar
    2 posts
    Member since:
    Oct 2019

    Posted 02 Jan Link to this post


    In our company, we have a lot of Telerik reporting templates, created with the visual studio designer tool and used for generating PDF.

    These reports contain several cultures support (localization) and images. We also have custom c# code in several events (ex: NeedDataSource event)

    We are migrating to .net core all our projects.

    I’ve tried a fist attempt to migrate to .net core, but I faced several issues:
    -The designer doesn’t work, but it’s “normal” as noted here…:
    -Localization doesn’t work. Surely linked to resource management change in .net core.
    -I had to remove images from the report template to avoid exception at runtime (because the designer embeds them into resx file)

    Before digging in more, Which is the best recommended way to migrate legacy report to .NET Core ? (And still have localization and custom code on events)

    When the .net core designer will be available?

    Thanks in advance,

  2. Neli
    Neli avatar
    255 posts

    Posted 06 Jan Link to this post

    Hello Frédéric,

    Currently, there is no design-time support for type reports in .NET Core projects. Note that there are certain limitations in the .NET Core framework that prevent us from implementing the .NET Core Visual Studio designer. You may find an explanation of the problems we hit in the Make Visual Studio designer work with .NET Core (a.k.a. SDK-style) projects feature request. I suggest also to vote for this feature.

    Recently, we tested to use the code of a CS report created in the Visual Studio in .NET Framework (e.g. copied and pasted the report code in a .NET Core ClassLibrary project), and we were able to use the report as it is, without removing the designer-specific code. This indicates that the .NET Core team is moving the design-time support forward. We need some more functionality to make our designer operative though. We are tracking the .NET Core team updates on their Windows Forms designer and will do our best to include VS Report designer support for .NET Core as soon as all the needed functionality is implemented.

    Basically, the resx files are resolved in a different way in .NET Core which causes the issue with the images and the localization. I suggest to convert the report to TRDP. However, you will need to use Expressions/ Binding instead of events. In addition, you will need to localize the reports again. You can also check the following feature request and vote for it Converting CS/VB report to TRDP report should preserve localization.


    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
  3. Frédéric
    Frédéric avatar
    2 posts
    Member since:
    Oct 2019

    Posted 22 Jan in reply to Neli Link to this post


    Thanks for this complete answer.

    The resx issue seems to be resolved using .NET Core 3


Back to Top