ActiveReports 17.0 Has Released

Posted by: alec.gall on 6 February 2023, 1:29 pm EST

    • Post Options:
    • Link

    Posted 6 February 2023, 1:29 pm EST

    ActiveReports 17.0 is live! This is our major version release for the year, and as usual, we will have 2 service packs coming later in the year.

    For more information on the new features arriving with 17.0, check out the release blog here: https://www.grapecity.com/blogs/activereports-net-v17-has-released

    ActiveReports 17.0 Download: https://cdn.grapecity.com/ActiveReports/ar17/ActiveReports-v17.0.0_light.exe

  • Posted 6 February 2023, 5:13 pm EST

    Is the ActiveReports 17 documentation still a work in progress? It seems to be kind of bare-bones, without remarks and examples.

    If you compare the AR 17 online help entry for the SectionReport Fields property ( https://www.grapecity.com/activereportsnet/docs/latest/online/GrapeCity.ActiveReports~GrapeCity.ActiveReports.SectionReport~Fields.html?highlight=fields%2C ) with that of the AR 16 version ( https://www.grapecity.com/activereportsnet/docs/versions/v16/online/GrapeCity.ActiveReports~GrapeCity.ActiveReports.SectionReport~Fields.html?highlight=fields%2C ) you will see what I mean.

  • Posted 8 February 2023, 5:52 am EST

    Hello!

    Thanks for pointing this out to us. I have escalated your concerns to the documentation team and the Product Manager and will get back to you once I have an update on the same.[ARDOC-4242]

  • Posted 8 February 2023, 11:49 am EST

    Hi,

    code-based SectionReports didn’t work in ActiveReports 17.0.0 and .NET 7!

    Is there any roadmap for this request available?

    Thank you.

  • Posted 9 February 2023, 4:06 am EST

    Hi Alexander,

    Please refer to the following forum post for reference:

    https://www.grapecity.com/forums/activereports/section-reports-dotnet-6-and-designer

  • Posted 9 February 2023, 10:11 am EST

    Hi Alexander,

    To elaborate further, we have been wanting to port Code-Based Section Reports to .NET 6/7 for a long time, but unfortunately we have been unable to due to some important parts of the SDK not being available in .NET 6/7 yet. We’ve been communicating with Microsoft about it and it has been getting pushed back over and over again. We were hoping to have it working for AR 17 as they had told us the SDK would have the necessary updates in November, but now that’s been pushed back to Spring 2023 again. I’m hopeful that this will be the last time it is pushed back and we will be able to implement this before AR 18, but unfortunately we are at the mercy of Microsoft until those updates are made.

    In the meantime, please follow the workaround that Askshay mentioned above. I apologize for the frustration in waiting for this to be available.

  • Posted 9 February 2023, 10:46 am EST

    Hi CLAS,

    Again, Thank you for pointing this out to us. We have re-added all the remarks and examples in the ActiveReports 17 Documentation.

  • Posted 20 June 2023, 6:05 am EST

    Where is the nuget package for GrapeCity.ActiveReports.Document? The last version is shown as 16.4.0 and this is preventing us upgrading beyond that (all the other v17 updates fail due to a dependency on this one)

    https://www.nuget.org/packages/GrapeCity.ActiveReports.Document

  • Posted 21 June 2023, 1:11 am EST

    Hi Simon,

    In ActiveReports 17 GrapeCity.ActiveReports.Document assembly and NuGet package are merged with GrapeCity.ActiveReports assembly and NuGet package.

    For more information please refer to the following pages of our documentation: Breaking Changes

    Regards,

    Akshay

  • Posted 22 June 2023, 9:59 am EST

    Thank you. I’d seen the breaking changes page but hadn’t appreciated that a nuget package manager update would fail as a result.

    In case it helps anyone else - the way to update these is to install the new 17.x version, then from VS use the “Tools → Upgrade to Active Reports 17” option to update.

  • Posted 26 June 2023, 2:43 am EST

    Hi Simon,

    Thanks for sharing your solution with us as it will others who might be doing something similar.

  • Posted 4 July 2023, 4:15 am EST

    Are there any release notes to tell us what is fixed in 17.1.2?

  • Posted 5 July 2023, 2:13 am EST

    Hello Simon,

    Following are the fixes that are implemented in ActiveReports v17.1.2:

    • [AR-30864] Winform project backend printing
    • [AR-30870] AR17, Server 2012R2: Standalone designer application throws exception releated to GetDpiForWindow function
    • [AR-30883] [AR17.1] Different proportions and spacing in reports printed in continuous and single-page modes from VS template WinViewer app
    • [AR-30955] Cannot save report when I set the PaperHeight to a large size
    • [AR-30781] FormattedText: HTML table appears garbled on preview and at design time
    • [AR-30828] [AR17.1.0-beta] Switch expression in category sort doesn’t work in chart
    • [AR-30835] [AR17.1.0 beta] Image nested to Table cell with property Autosize and Alignment to center and middle, the alignment does not take effect in Preview and Export
    • [AR-30837] [AR17.1.0-beta] Tablix cell value reference doesn’t work in case of column grouping
    • [AR-30862] [Demo site] Reports with custom fonts exported to PDF/Tiff without content
    • [AR-30895] [AR17.1]JSViewer: Dashboard toolbar is not displayed after ‘Jump to report’ and returning back
    • [AR-30921] [AR17.1] RPX report with chart and decoration not rendered in JSViewer/WebDesigner in CrossPlatform mode
    • [AR-30930] [AR17.1] 404 Error appears upon browsing through IIS JSViewer MVC sample published to folder
    • [AR-30931] [17.1] Section Report does not connect to .mdb (OLEDB JET) data source
    • [AR-30964] [PageReport] Unable to render report when all columns of TableHeaders and rows(>1) are merged
    • [AR-31041] Problems with some references in non Core samples
    • [AR-31067] [AR 17.1] Pdf export return exception with ‘The object is disposed’ message when two exports as Task
    • [AR-30782] WpfViewer: the page’s contents appear cropped in multipage view, continuous view(depeding on window size)
    • [AR-31046] Incorrect Field Names when using XML Data in Section Reports

    Regards,

    Anand

Need extra support?

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

Learn More

Forum Channels