Extension Conflict?

Posted by: peter.herschel on 8 August 2022, 4:52 am EST

    • Post Options:
    • Link

    Posted 8 August 2022, 4:52 am EST

    I’ve installed AR16.1.3 into visual studio 2022 17.2.6. I then created a NET Framework 4.8 project and added a section report. When compiled, I received warnings until I upgraded Microsoft.Bcl.AsyncInterfaces and System.Runtime.CompilerServices.Unsafe from version 5 to 6.

    The section report designer and test application working fine.

    I then installed Devart LinqConnect version 5. When their extension Devart.EntityDeveloper.VSPackage https://www.devart.com/entitydeveloper/ is enabled, I am unable to design sections reports. I get “The designer could not cast the report to the SectionReport type. The probable cause is that the SectionReport assembly reference was not set to CopyLocal True. “

    If I disable the devart.entitydeveloper extension and restart visual studio, I can design reports again. The devart Entity Developer extension works just fine.

    Are extension conflicts common - any suggestions?



  • Posted 9 August 2022, 8:25 pm EST

    Hi Pete,

    >> The probable cause is that the SectionReport assembly reference was not set to CopyLocal True.

    I wasn’t able to replicate this behavior on my end. I tested this out with the latest version of Visual Studio 2022 which is 17.3 and Entity Developer Extension Version 7.0.0. The Report designer seems to open fine for SectionReports. Please try out the latest version of Visual Studio and Entity Developer extension and let us know if the issue persists.

    If you are using a .licx file to license your project please remove the version, cultural, public token key specification from all the ActiveReports license entries.

    For Example:

    Say you have this entry in your licenses.licx file:

    GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win, Version=, Culture=neutral, PublicKeyToken=cc4967777c49a3ff

    Try changing it to:

    GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win

    Please share you the packages.config file and licenses.licx file(if any) of your project as well and a video demonstrating this issue so we can investigate further on this and help you resolve this issue.

  • Posted 12 August 2022, 1:16 am EST

    I have a video link here https://1drv.ms/a/s!BAMvFhpIZccxg8J07Kb-qwC3u5l9mw as it was too large to upload.

    The product has 2 extensions as you will see.

    • LinqConnect
    • ORM Designer (this conflicts for me)

    I tried editing the license files - with no effect. Note: the report runs fine even when the designer cannot edit the report.

    I installed by via purchasing the software (LinqConnect standard), vendor download, then install which recreated the two extensions seen in the video. The Devart extensions work without any errors.



  • Posted 15 August 2022, 11:15 pm EST

    Hi Pete,

    Thanks for the information. I have shared your request with the development team and will get back to you once I have any update on the same. [AR-29191]

  • Posted 26 April 2023, 4:59 am EST

    Hi Pete,

    Can you please share the Devart extension file causing the issue?

    You may upload the extension file on the following page: My Upload

    Let us know once you have uploaded the file and I will download it from our end. Also As ActiveReports 16.4 and 17.0.3 is now released. Can you please let us know if you are able to reproduce this issue with the latest versions as well.

    You may download ActiveReports 16.4 and ActiveReports 17.0.3 from the following page: https://www.grapecity.com/activereports/download-version-history

  • Posted 26 April 2023, 10:42 pm EST - Updated 26 April 2023, 10:44 pm EST

    The extension is added as part of the devart LinqConnect product install. The product installs 2 extensions. You can install the free version to test. see: *https://www.devart.com/linqconnect/

    The issue occurs with the newer versions also. The issue only occurs with code based section reports within visual studio.

  • Posted 27 April 2023, 8:08 pm EST

    Hi Pete,

    Thanks for the information. I have discussed with the development team on this. With the current limitations of the Code-based Section Report Designer it seems it is not possible to create a fix in the designer we are rather planning to create a new out-of-process designer which is currently under investigation for .Net Core as any other possible solution will require changes in the Devart Extension.



Need extra support?

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

Learn More

Forum Channels