.NET Core

Posted by: mark.hodgson on 26 July 2019, 12:53 am EST

    • Post Options:
    • Link

    Posted 26 July 2019, 12:53 am EST

    I’ve seen examples suggesting how to run reports in a Framework project and call them separately from your Core app.

    Most of our projects that contain reports that do not use SQL data sources, rather they use a tree (or graph) of objects (what you might once have called a tree of business objects) and it’s useful for us for the reporting to be in the SAME project with the web API, objects and associated object repositories etc. so they can share code. We genrally producve PDFs on the server - so Javascript viewers that are not reliant on .Net Framework are of little use.

    Using .NET Core presents a problem since AR is a Framework library.

    The next version of .NET Core will skip version 4 and drop the “core” moniker to become simply .NET 5. So it seems that the .NET Framework is being driven into the sidings, destined to be deprecated or at least merely maintained and not actively developed. More and more developers will be leaving the old Framework behind.

    So where does this leave Active Reports?

    Our company pays a lot of money in annual support for AR and it seems a bit of a raw deal while the tools we’re paying for slip slowly into irrelevance…

    So, do you have imminent plans to implement Active Reports for .net Core?

    I’ve looked at some of the code for Active Reports and it looks pretty dated these days - which is surprising given the high version number. Could it be that people like us are just paying a high fee for you to recompile and re-package the same old faithful reporting code each time there’s a new version of Visual Studio? Sounds like money for old rope.

  • Posted 28 July 2019, 5:54 pm EST

    Hello Mark,

    Support for Asp.Net core is scheduled to release in our next release i.e AR14. AR14 will also support the desktop pack of .Net core. However, Section Report will only support desktop pack of .Net Core, not Asp.Net Core.

    Thanks for your valuable feedback. I have forwarded this to our product team and will inform you once I get any reply from them.

    Also, there are many features which introduce in AR13 along with VS2019 support:

    1. Web Designer: You can embed Web Designer into any web application to create and edit reports effortlessly.
    2. JS Viewer: A new generation viewer which is built on JavaScript library
    3. DV Chart: A new Chart control that provides ease of data visualization through encodings

      and many more…

      You can refer to the following documentation link to find more information about new changes in AR13


    Please feel free to revert back if you still have some question regarding this. I am more than happy to help you.


  • Posted 29 July 2019, 2:38 am EST

    Hi Mark,

    Thanks for voicing your concern. However, you can rest assured that we are, and have been, continuously developing ActiveReports to meet our customers’ and market demands. Regarding the code remaining the same, we try our best to keep the API similar to minimize any learning curve for our users. I hope that has been case for you.

    As Mohit mentioned, we are planning major features in the coming release of AR14, with .NET Core and .Net Core 3 support being part of them. I will also clarify that, while Section Report support will not be available in .NET Core in AR14, we are looking to include them in the following release of AR.

  • Posted 17 December 2019, 2:55 pm EST


    I am glad to tell you that AR14 is release now which includes the supports of .Net core. For more information , you can refer the following link:



    Also, you can download the trial version of AR14 from the following link:




  • Posted 1 April 2020, 4:55 am EST

    We are running into some similar challenges with .net core and was curious if there was an estimated timeline for support of .Net Core in section reports outside of the desktop pack of .Net Core Thanks

  • Posted 1 April 2020, 6:38 pm EST


    Currently, there is no estimated timeline for this. Support of section report in asp.net core will include in AR15/AR16.

    Sorry for the inconvenience caused to you.



  • Posted 13 April 2023, 5:46 pm EST

    Well, we’re on AR 17 now and still you cannot create a section report in a .NET 5, 6 or 7 project, according to: https://www.grapecity.com/activereportsnet/docs/latest/online/section-report-type.html

    “Note: In Visual Studio 2022, only .NET Framework 4.7.2 and 4.8 are supported for code-based section reports.”


  • Posted 2 May 2023, 2:24 am EST

    We too need to have some functionality to develop or maintain code based section reports in net 7+. This has been a stumbling block for us. If it meant removing preview tab and have the designer only then we would be back in business.

  • Posted 3 May 2023, 3:37 pm EST


    For designing Code-based Section Reports in .Net 5, 6 or 7 please refer to the following workaround: Designing Code-based Section Reports in .NET Core | ActiveReports 16 .NET Edition

    With the above workaround you will be able to design and preview section reports. For more information, on this limitation please refer to the following forum case as we have discussion about this limitation detail there: Section reports, dotnet 6 and designer



  • Posted 3 May 2023, 6:36 pm EST

    Yeah, setting reports up in a separate .NET Framework project is what we’ve been doing - and frankly, it’s a huge pain in the arse.

    Why is it not possible to implement this feature in .NET ‘core’? I recall some older (much older) thread on here containing a reply suggesting it was due to a bug waiting for a Microsoft fix. A responder queried what this bug might be and if maybe someone could chip in and help - and of course there was no reply to this - making me think it was just a deflection tactic.

    Been waiting a few versions of AR now and it seems pretty clear that section reports are not and will not ever be supported in .NET versions past 4.

  • Posted 4 May 2023, 6:24 pm EST


    >> Why is it not possible to implement this feature in .NET ‘core’? I recall some older (much older) thread on here containing a reply suggesting it was due to a bug waiting for a Microsoft fix.

    First of all, I would like to apologies for the inconvenience this has caused you. We are not trying to deflect any questions of customer queries. We try our best to ensure there is transparency between the product team and the customers and we are sorry if we have failed to do so in this case.

    The Microsoft issue we are referring to is posted here #4126 (Microsoft Internal). Currently, we are still waiting on Microsoft to implement the necessary designer features for this functionality to be possible. They have pushed back the release time for the necessary updates multiple times.

    We will definitely include support for designing Code-based Section Report in .Net environment in the coming future(maybe ActiveReports 18).

    We request you to be patient in the matter we are not ignoring or neglecting section reports we would love to implement this feature as soon as possible. We are just at the mercy of Microsoft at the moment. We are also currently investigating on the idea to re-design a new out of process designer for Code-based Section reports in .Net environment. We strongly believe that we will have something for you by the end of this year or in the first quarter of next year in ActiveReports 18.

  • Posted 4 May 2023, 6:30 pm EST


    Thanks for the reply and the information. Sorry if I sounded a bit grumpy. We’ve been using AR since ditching Crystal Reports in the pre-dotnet VB6 days. Although somewhat ironically the problems we had with CR, i.e. the plethora of COM DLLs and associated deployment and upgrade headaches seem to have resurfaced in AR with dozens of interrelated Nuget packages!


Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels