Licensing issues with .NET Core

Posted by: mike.killey on 16 November 2020, 10:02 pm EST

  • Posted 16 November 2020, 10:02 pm EST


    I am experiencing a number of issues relating to licensing within a .NET Core project for use with the JSViewer. I am currently within the trial period for ActiveReports, but I understand this shouldn't be the cause.

    I have a Core 3.1 project (copied from the WebSamples14/JsViewerSamples/JSViewer_Vue(Core) sample project on Github). This sample uses embedded templates, but I would like to use the custom store option instead (settings.UseCustomStore). On running this, within the method called to return the PageReport, as soon as my code tries to new up a PageReport, I get an exception that GrapeCity.ActiveReports.Licensing cannot be found - which I understand.

    The solution to this should just be to include a licences.licx embedded file and rebuild. But when I do this, Visual Studio 2019 fails to build because the LC.EXE command line is longer than 32000 chars. This is because of the large number of packages required just by ActiveReports alone, never mind any additional packages I require as part of the project. No matter what I have tried to do to fix this, I simply cannot get a NET Core project to build with a license.licx embedded file. I have tried the option to create a .gclicx file instead, but that doesn't seem to work either (this is a single project solution).

    To test whether this is isolated to NET Core, I have recreated the same project with .NET 4.7.2. With the embedded licence.licx file - I have no problems at all and the CustomStore option works as intended without any licencing exceptions or errors. This is not an ideal solution for me as I would prefer to use NET Core for this project.

    I am happy to package up my test projects if required, but you should be able to recreate simply from the above mentioned sample project on GitHub.


  • Replied 17 November 2020, 2:33 am EST

    Ok, I think I've managed to crack this one now. From reading other posts (mainly in the ActiveReports v7+ area), I can identify a number of issues.

    1. There is a problem with the latest version (v14.2.2603) of the AspnetCore.Viewer package which means that it throws Licensing exception during runtime.
    2. The documentation is terrible
    3. The documentation is terrible

    Now I can see that I've listed twice that the documentation is terrible, but this is an important one, and one that has caused me to waste 4 days effort on trying to resolve this. The docs state that you need to add a licenses.licx file to resolve licensing issues, but (and it's a big but) - this is not necessary for .NET Core projects. It's not stated explicitly enough that the GCLM is already doing all the licensing stuff during build, which mitigates the need to add the licx file (and breaks the build). The docs need much more clarity around the whole process for .NET Core projects. I probably wouldn't be in this position if it wasn't for the broken v14.2.2603 package.
  • Replied 17 November 2020, 12:55 pm EST

    Hi Mike,

    We encountered the exactly same issues when trying to "License to .NET core project"!
    But you mean this is a known issue for AspnetCore.Viewer package(v14.2.2603) that could not be resolved by us?
  • Replied 17 November 2020, 8:43 pm EST

    I don't know if it is a known issue by the AR devs, but all I can say is that using the previous version (v14.2.2544) has resolved it temporarily for me.
  • Replied 18 November 2020, 2:23 am EST

    Hello Mike,

    We are very sorry for the inconvenience caused to you. I am able to reproduce the issue at my end with .Net core project. I have escalated the issue to the development team and will inform you once I get any information form them.

    Also, I will share the feedback with concerned team about the documentation issue.

Need extra support?

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

Learn More

Forum Channels