These issues relate to licensing old versions of ComponentOne applications prior to 2020 v2, as well as legacy products such as .NET 2.0, .NET 4.0, ActiveX, Silverlight and LightSwitch.

Issue 1: I have a licensed version of a ComponentOne product but I still get the splash screen when I run my project.

Solution: If this happens, there may be a problem with the licenses.licx file in the project. It may not exist, it may contain incorrect information, or it may not be configured correctly.

First, try a full rebuild (Rebuild All from the Visual Studio Build menu). This will usually rebuild the correct licensing resources.

If that fails too, follow these steps:

1. Open the affected project.
2. Select an instance of the updated component.
3. In the Visual Studio Properties window, change any property. It does not matter which property you change; you can change it back to the previous value.
4. Rebuild the project using the Rebuild All option (not just Rebuild) and run the solution.

Alternative 1: Follow these steps:

1. Open a new Visual Studio project.
2. Add the updated component to the form.
3. Compile and run the new project.
4. Open the licenses.licx file in the new project.
5. Copy the line that starts with the namespace of the updated component (for example, C1.Win.C1Report) and ends with a public key token.
6. Open the existing, incorrectly licensed project.
7. Open the licenses.licx file in the new project.
8. Paste the copied line from step 5 into this file (replace the old licensing information with the new).
9. Rebuild the project using the Rebuild All option (not just Rebuild) and run the solution.

Alternative 2: Follow these steps:

1. Open the affected project.
2. Delete the licenses.licx file from the project.
3. Add a new instance of the updated component to the form.
4. Rebuild and run the solution. The nag screen should not appear.
5. Remove the newly added component from the form.

Try each of these options multiple times, if necessary. Still if that does not help, it is a possibility that you are creating the controls through code rather than design-time? If so, you must add an entry for the control in the licenses.licx file or create a licenses.licx file manually. Also if this is a website, and not an ASP.NET web application, try right-clicking the licenses.licx file and selecting "Build Runtime Licenses" from the context menu.
To manually create a licenses.licx file in Visual Studio, follow these steps.

1. Right click your solution and choose "Add," and "New Item"
2. Choose "Text File" and click "Add"
3. Right click the file and choose "Rename"
4. Rename the file to "licenses.licx"
5. Double-click the file to open the text editor
6. Enter the Class and Assembly name

The licenses.licx file is simply a text file and one that is created manually will produce the same results as one which is automatically generated.

You can also create the licenses.licx file in Notepad or another text editor, then, in Visual Studio, right click the solution, click "add" and "existing item" and browse to the file you created.

You can also create the licenses.licx file in Visual Studio. Simply add the controls you need to license to a new application, double-click the licenses.licx file that is generated, and copy/paste the information.

To use the licenses.licx file in a non-Visual Studio application, simply create the text file using the instructions above, and add the file to your compiler according to the user manual.

Issue 2: I have a licensed version of a ComponentOne product on my Web server but the components still behave as unlicensed.

Solution: There is no need to install any licenses on machines used as servers and not used for development.

The components must be licensed on the development machine, therefore the licensing information will be saved into the executable (.exe or .dll) when the project is built. After that, the application can be deployed on any machine, including Web servers.

For ASP.Net 2.x applications, be sure that the App_Licenses.dll assembly created during development of the application is deployed to the bin application bin directory on the Web server.

If your ASP.Net application uses WinForms user controls with constituent licensed controls, the runtime license is embedded in the WinForms user control assembly. In this case, you must be sure to rebuild and update the user control whenever the licensed embedded controls are updated.

Issue 3: I clicked on the OK button in the C1LicenseActivation window and nothing happened.

Solution: Make sure that the file C1Licensing.exe is in your bin folder (for example: C:\Program Files\ComponentOne\WinForms Edition\bin 2.0). If this file is not on your machine, you can obtain the latest version from http://prerelease.componentone.com. If problems persist, please contact the MESCIUS support team.

Issue 4: I received an error that my serial number is invalid.

Solution: Click on the About button for the control you're trying to license and identify the version number. If the control is a 2007 v3 control or earlier, then you should only enter the first 17 characters of your serial number. If it is 2008 v1 or later, you should your full serial number (if your serial number is from 2008 v1 or later it will be 28 characters; otherwise it will be 17).

Contact Our Support Team

Get in touch with our support team and we will help resolve your licensing issue.