GCLICX File for DLL

GCLICX File for DLL

Posted by: planctot on 30 June 2023, 2:58 am EST

• 

  planctot

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 30 June 2023, 2:58 am EST

  Hi,
  
  We are using AR15 in a series of DLLs that are consumed by a web application. I’ve been able to get the licensing to work through the use of a .gclicx file generated for one of those DLLs (as a test run), however, it appears that all of the DLLs are working, even though I generate the .gclicx file for only one of them. Can you please explain why this is occurring, and whether or not we should add the .gclicx file for each of our DLLs which reference AR15 packages.

          Thank you,
                    Patrick
  

• 

  anand.sinha

  

  • Post Options:
  • Link
    Copy

  Posted 2 July 2023, 11:45 pm EST

  Hi Patrick,

  This could occur due to a few possible reasons, for example, if the ‘.gclicx’ file has been generated for the DLL that references other DLLs which use ActiveReports components then you do not require multiple ‘.gclicx’ license files.

  However, if you use each DLL (which references ActiveReports) separately in your web application then you need to generate a separate ‘.gclicx’ license file for each of your DLLs.

  We’ll however suggest you do create a ‘.gclicx’ license file for each of your DLL that references ActiveReports.

  Regards,
  
  Anand