ActiveReports 14
ActiveReports 14 User Guide / License Your ActiveReports
In This Topic
    License Your ActiveReports
    In This Topic

    You can use the GrapeCity License Manager utility to license ActiveReports during installation or if you already have a trial version installed. This topic gives an overview of all aspects of licensing in ActiveReports.

    License Types

    See ActiveReports Editions to learn which features are exclusive to the Professional Edition.

    License Type Description
    Evaluation

    Trial key is required. Evaluation banners display on all reports and controls, and the product stops functioning after 30 days from the date of installation. The first key is already activated when you download the trial. If needed, you can request a new key from the Sales department for an additional 30 day trial.

    Standard

    Standard Edition product key is required. Evaluation banners appear only on features that are exclusive to the Professional Edition. You receive this key by email when you purchase ActiveReports Standard Edition or upgrade from a previous version of ActiveReports Standard Edition.

    Professional

    Professional Edition product key is required. All reporting functionality and controls appear without any evaluation banners. You receive this key by email when you purchase ActiveReports Professional Edition or upgrade from a previous version of ActiveReports Professional Edition.

    If you cannot find your email with the product key, please contact activereports.sales@grapecity.com to have it looked up.

    Licensing a Developer Machine

    Note that any machine on which ActiveReports are opened in Visual Studio or on which ActiveReports projects are compiled in Visual Studio must be licensed.

    Tip: Always run the License Manager as Administrator.

    To license a machine with ActiveReports during installation or to license a trial without reinstalling

    1. From the Start menu, go to GrapeCity License Manager to open the licensing manager window. During installation, the window appears automatically.
    2. In the GrapeCity License Manager window, click Activate.


    3. Enter the serial key exactly as you received it from GrapeCity, including any capital letters, and click Activate.  

    4. The activation message appears. Click OK to complete the licensing process.
      To see the license details such as the license type (Trial or Product), edition (Professional or Standard), and the date of activation and expiry, click Details in the licensing window.

    To license ActiveReports on a machine without an internet connection

    1. From the Start menu, go to GrapeCity License Manager to open the licensing manager. During installation, the window appears automatically.

    2. In the GrapeCity License Manager window, if you enter a key and click Activate, a network error is shown. In this case, click Offline Activate.

    3. Copy the Activation Key.
    4. On another machine with an internet connection, visit website https://sa2.grapecity.com and select Activate. Remember not to close the activation dialog on your original machine until the activation process is complete.

    5. Enter the Activation Key you copied in step 3 on the website, and again click Activate.
    6. After successful activation on the website, copy the License Data from the website and paste it in the licensing window.
    7. Click Activate and then OK to complete the licensing process.

    To activate a license for ActiveReports on multiple machines

    You can only activate a single developer license key for ActiveReports on three machines for use by one developer.

    If you have used all three of the license activations and you want to license a fourth machine, for example, a virtual machine for use by the same licensed developer, you must deactivate the license key from one of the other machines. For more information, drop down the section below titled "To deactivate an ActiveReports license."

    After you have deactivated licensing on one of the machines, you can activate ActiveReports on another machine.

    Note: Deactivate your ActiveReports license before formatting a machine to avoid loss of activation. If this happens by accident, you can contact our support team for help.

    To deactivate an ActiveReports license

    To use your ActiveReports license on another machine  for your own use when you have used up all three of your activations, you can deactivate it on one machine.

    1. From the Start menu, go to GrapeCity License Manager to open the licensing manager window.
    2. In the GrapeCity License Manager window, click Deactivate.
    3. In the Deactivation page that appears, again select Deactivate to confirm the deactivation.
    4. Click OK to complete the deactivation process.

    To upgrade or downgrade a license

    Note: In order to upgrade or downgrade a license on a machine, you must have installed both a Professional and a Standard license on the machine. If you have not, the Upgrade/Downgrade column does not appear in the License Manager. If you have one and wish to install the other, you must first deactivate the installed license. The Upgrade/Downgrade option is added at that point.

    If you want to change your ActiveReports license type you need to do one of the following:

    Upgrade from a Standard to a Professional License:

    1. From the Start menu, go to GrapeCity License Manager to open the licensing manager window.
    2. In the GrapeCity License Manager window that appears, under Upgrade/Downgrade click Upgrade to Professional License.
    3. Follow the activation steps from step 3 of To license an ActiveReports Trial without reinstalling to upgrade.

    Downgrade from a Professional to a Standard License:

    1. From the Start menu, go to GrapeCity License Manager to open the licensing manager window.
    2. In the GrapeCity License Manager window that appears, under Upgrade/Downgrade, click Downgrade to Standard License.
    3. In the Deactivate ActiveReports 14 page that appears, select the Next button.
    4. In the Confirm the Product screen that appears, confirm that the correct product is being downgraded and click the Next button.
    5. The Deactivation Successful screen appears with the Product Name as ActiveReports 14 and the Current Status as Standard License.

    Note: You can upgrade a license only if you buy an upgrade from Standard Edition to Professional Edition.

    To determine whether a machine is licensed

    1. In Visual Studio, open any sample from the included samples located in C:\Users\USERNAME\Documents\GrapeCity Samples\ActiveReports 14.
    2. Open one of the reports in the sample and click the Preview tab.
    3. Scroll to the bottom of the report. If there is red evaluation text, the machine is not licensed.

    Note: To check for Professional Edition licensing, open a sample from the Professional folder, run it, and look for evaluation messages.

    Licensing a Project

    Tips:

    • To deploy using XCOPY, you must include the DLLs for all of your ActiveReports references in your bin/debug folder. To do this, in the Visual Studio Solution Explorer, select each reference, and in the Properties window, set Copy Local to True and rebuild your solution.
    • To avoid having to change the version number every time you install an ActiveReports service pack, in the Visual Studio Solution Explorer, select each reference, and in the Properties window, set Specific Version to False.

    To license Windows Forms projects made on the trial version

    These steps assume that you already have an ActiveReports licensed edition installed on your system.

    1. Open the project in Microsoft Visual Studio.
      Note: If another application calls the one containing ActiveReports features, you must license the calling application to avoid evaluation banners after deployment.
    2. Go to the Visual Studio Build menu and select Rebuild Solution.
    3. To verify that the application is licensed, open the licenses.licx file and compare it to the Required references section below.

    The executable application is now licensed, and no nag screens or evaluation banners appear when you run it. You can distribute the application to unlicensed machines and no nag screens or evaluation banners appear.

    Required references in the licenses.licx file (for Standard and Professional Editions)

    The licenses.licx file must contain the following references to ActiveReports if you were using both Section and Page reports, and both Windows and WPF viewers. See the table below for the references to the ActiveReports version and the reference to the Viewer control.

    Note: The Version, Culture, and PublicKeyToken information is added automatically, but can be removed, and should be removed if the version is wrong.
    Paste INSIDE the licenses.licx file.
    Copy Code
    GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports
    GrapeCity.ActiveReports.PageReport, GrapeCity.ActiveReports
    GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win
    GrapeCity.ActiveReports.Viewer.Wpf.Viewer, GrapeCity.ActiveReports.Viewer.Wpf                                        
    

    Here are all of the license strings that you may need:

    Component License String
    Section report engine GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports
    Page and RDL report engine GrapeCity.ActiveReports.PageReport, GrapeCity.ActiveReports
    WinForms viewer control GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win
    WPF viewer control GrapeCity.ActiveReports.Viewer.Wpf.Viewer, GrapeCity.ActiveReports.Viewer.Wpf
    PRO (some features) PDF export GrapeCity.ActiveReports.Export.Pdf.Section.PdfExport, GrapeCity.ActiveReports.Export.Pdf
    PRO ONLY: WebViewer, HTTP handlers GrapeCity.ActiveReports.Web.WebViewer, GrapeCity.ActiveReports.Web
    PRO ONLY: End-user designer GrapeCity.ActiveReports.Design.Designer, GrapeCity.ActiveReports.Design.Win

    PRO ONLY: JS Viewer

    GrapeCity.ActiveReports.Aspnet.WebViewer, GrapeCity.ActiveReports.Aspnet.Viewer
    PRO ONLY: Web Designer GrapeCity.ActiveReports.Aspnet.WebDesigner, GrapeCity.ActiveReports.Aspnet.Designer

    Note: When using the PDF export filter in your project, make sure you check the licenses.licx file for reference to the PDF Export Assembly.

    To license Web Forms projects made on the trial version

    Follow these steps after you license ActiveReports on your machine.

    1. Open the project in Microsoft Visual Studio.
    2. Open the Visual Studio Build menu and select Rebuild Solution.
    3. The web site application is now licensed. You can distribute the web site application to unlicensed machines and no evaluation banners appear.

    To license Web Site applications

    Follow these steps after you license ActiveReports on your machine.

    1. Open the project in Visual Studio.
    2. In the Solution Explorer, right-click the licenses.licx file and select select Build Runtime Licenses to create the App_Licenses.dll file.

    The web site application is now licensed. You can distribute the web site application to unlicensed machines and no evaluation banners appear.

    To license a class library project

    Follow these steps after you license ActiveReports on your machine.

    1. Open the project for the root-level calling application, that is, the executable that calls your class library, in Visual Studio.
    2. From the Project menu, select Add New Item, and the select an ActiveReports report. (You can delete it later. This is only to add the references to the project.)
    3. Open the Visual Studio Build menu and select Rebuild Solution.
    4. Check the licenses.licx file and verify that ActiveReports licensing is added for all of the features used in your project.
    Note: If you use other ActiveReports features in your class library that are still showing an evaluation banner, for example, features exclusive to the Professional Edition, you can add those references manually and rebuild the solution.

    To license a project that use Web Designer and JS Viewer nuget packages

    The Web Designer and JS Viewer nuget packages do not include a licenses.licx file, so the file needs to be added and configured manually in your project. Follow these steps to add license file in your Web Application in Visual Studio:

    1.            
    2. Go to Project menu and select Add New Item.
    3. Select a new text file and rename it licenses.licx.
    4. Open the blank licenses.licx file and populate the file with following entries:
      Paste INSIDE the licenses.licx file.
      Copy Code
      GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports
      GrapeCity.ActiveReports.PageReport, GrapeCity.ActiveReports
      GrapeCity.ActiveReports.Export.Pdf.Section.PdfExport, GrapeCity.ActiveReports.Export.Pdf
      
    5. Run the project.
      There should be no licensing errors, assuming that you already have a licensed ActiveReports Professional Edition.

    Licensing Errors

    Here are some common licensing errors and their causes.

    Error Cause
    Application cannot run because it was built with no license. Licensing is not present in the application or the calling application. See below for information on how to license the calling application.
    License for XXXX (control name) could not be found. Extra lines for components that you do not use are in the licenses.licx file. Delete unnecessary information and Rebuild the project.
    Licensing has not been correctly applied to the application. Check the three key points below.
    Exception (LicenseException) Check the three key points below.
     'No License' message on running .NET Core applications in Visual Studio 2017 This is so because Visual Studio 2017 does not support core license compilation.
    1. Ensure that the license file is added to the appropriate project.

      The licenses.licx file is automatically generated in the project where ActiveReports is used. But if your application is composed of multiple projects and another project calls the reports defined in your class library, you need to register it in the calling project rather than just in your report project.

      When you add an ActiveReports web service to a Page report, RDL report, or XML-based Section report project, the licenses.licx file is not created automatically, and the license strings are not added. You also need to manually add licensing to your application if you want to create a control at run time or use the HTTP handlers.

      To manually add licensing to the calling application

      Note: In a C# Windows Forms project, the license file is in the Properties folder. In a Visual Basic project, it is in the My Project folder.

         1.  In your application that contains ActiveReports components, check that the proper licensing strings are in the licenses.licx file. (See the table of license strings below.)

         2.   Copy the ActiveReports strings from the file into the licenses.licx file in the calling application.
              a.   If there is no license file, from the Project menu, select Add New Item.
              b.   From the listed templates, select Text file and change the name to "licenses.licx."
              c.   In the Solution Explorer, double-click the newly created licenses.licx file to open it, and paste in the licensing strings for all components you use.

         3.   From the Build menu, select Rebuild Project to embed the licensing.

      ​Note: If your project is a web site, the bin folder has the licenses embedded in the App_Licenses.dll file.

    2. Ensure that the contents of the license file are correct.

      Depending on which features of ActiveReports you use in your application, the license file may need to contain multiple license strings.

      You will find a full list of license strings that you may need in the Required references in the licenses.licx file (for Standard and Professional Editions) section above.

    3. Ensure that the Build Action property is configured correctly for the license file.

      1.  In the Solution Explorer, select licenses.licx (you may need to click the Show all files button to see it).

      2.  In the Properties window, ensure that the Build Action property is set to Embedded Resource.

    4. Ensure that .NET Core applications are always run on Visual Studio 2019        

      .NET Core applications should be run only in Visual Studio 2019 since Visual Studio 2017 does not support core license compilation.