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