We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

How do I enable licensing to Syncfusion controls in Visual C++ applications?

 

The following are the steps to be followed to resolve the licensing error for the Syncfusion Controls in Visual C++ Projects. These steps assume that the user is using the version 4.2.0.37 and .Net Framework 1.1.

Step 1:

Build the Visual C++ Project that contains the Syncfusion controls. It will request some licensing checks and then a TestApplication.exe will be created in the output folder.

Step 2:

Unzip the genlic.zip(http://www.syncfusion.com/Support/user/uploads/genlic_5318b61f.zip) file to the project output folder, where the TestApplication.exe is located. Check the controls.txt file, and edit the version for your framework (As said above, we have assumed framework as 1.1 hereafter).

  • Version=4.200.0.37 - if working with .NET Framework 1.0
  • Version=4.201.0.37 - if working with .NET Framework 1.1
  • Version=4.202.0.37 - if working with .NET Framework 2.0

Step 3:

Open Visual Studio .NET 2003 Command Prompt and type lc.exe. This is to verify that the lc utility under the 1.1 framework is configured in the user's system.

lc.exe verification.Step 4:

In the command prompt, navigate to the output folder and run genlic.bat with the Application.exe as its argument.

[Command Prompt]C:\TestApplication\debug>genlic.bat TestApplication.exe

*.Exe.Licenses file creation.Step 5:

The TestApplication.exe.licences file will be generated in the output folder. Copy the TestApplication.exe.licences to the folder where the solution file resides.

Step 6:

Open the Property Pages and select Linker --> Input --> Embed Managed Resource File. Type $(SolutionDir)TestApplication.exe.licences and click 'Apply' and 'Ok'. The $(SolutionDir) is a macro that returns the directory path where the solution file resides. This step will embed the licensing information (*.exe.licenses) in to the exe file.$(SolutionDir)TestApplication.exe.licenses is equivalent to C:\TestApplication\TestApplication.exe.licenses

Project Properties setting.Step 7:

Rebuild and run the application. The licensing error popups will be suppressed this time.

Please note:Issue 1:

If the user tries build the *.exe.licenses file with reference to the wrong version of Syncfusion.Core, he will be encountered with the following error.

Controls.txt(1) : Error LC0003: Unable to resolve type 'Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core, Version=4.202.0.37, Culture=neutral, PublicKeyToken=632609b4d040f6b4'

The user have used 4.202.0.37 instead of 4.201.0.37 while building the *.exe.licenses with 1.1 Framework.

Error in building *.exe.licenses.Issue 2:

Even after changing the version information, if the build reports the same error, the problem is there with your Syncfusion Essential Studio installation. Inorder to avoid this, please follow the steps shown below.

  • Please rename the following folders {Install Drive}:\Program Files\Syncfusion\Essential Studio\Assemblies and {Install Drive}:\Program Files\Syncfusion\Essential Suite\Assemblies, if found in the system. This is to make sure that the assemblies for the project are picked up from the public assemblies(C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\PublicAssemblies) folder alone.
  • Run the AssemblyManager from the Start --> All Programs --> Syncfusion --> Essential Studio 4.2.0.37 --> Utilities --> Assembly Manager.
  • In the AssemblyManager, select the 'Remove All Versions' option and then click 'Perform Action'. This will remove all the Syncfusion assemblies from the GAC(C:\Windows\Assembly) and the public assemblies folder({Install Drive}:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\PublicAssemblies).
  • Then in the AssemblyManager, select the 'Install version 4.2.0.37' option and then click the 'Perform Action'. This will install the Syncfusion assemblies of version 4.2.0.37 in the GAC and the public assemblies folder.
  • Follow the steps from the beginning after deleting the output directory(TestApplication/debug folder in this case).

Error in build even after changing the version information.

Article ID: Published Date: Last Revised Date: Platform: Control:
935 04/30/2011 07/10/2014 Miscellaneous Install and Configuration
Did you find this information helpful?
Add Comment
You must log in to leave a comment

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.