GrapeCity, Inc., publishes the ComponentOne product line.

  • Licenses are per-developer. A developer may install their license on up to three machines.
  • Licenses may be transferred from one developer to another or from one server to another. In this case, the original copy must be completely removed from the original developer's machine (or from the original server).
  • A license entitles you to build applications using our components. The applications you build can be distributed royalty-free.
  • A license entitles you to one year of free upgrades, including bug fixes and new features. After one year, you are no longer entitled to updates, but you may continue to use the products received with your ComponentOne Studio subscription after your subscription has expired.
  • Source code is not included with any products unless explicitly stated in the product feature list. Exceptions to this rule are the source for the Report Designer application, which is included in the ComponentOne Studio WinForms Edition.
  • Volume discounts are available. Please contact sales for details.
  • Commercial OEM License: If you want to use ComponentOne to create your own commercially licensed SDK, choose the Commercial OEM license. Since use cases vary widely, OEM licenses are customized for each customer. Contact us for more information.


Licensing is a mechanism used to protect intellectual property by ensuring that users are authorized to use software products.

Licensing is not only used to prevent illegal distribution of software products. Many software vendors, including GrapeCity, use licensing to allow potential users to test products before they decide to purchase them.

Without licensing, this type of distribution would not be practical for the vendor or convenient for the user. Vendors would either have to distribute evaluation software with limited functionality, or shift the burden of managing software licenses to customers, who could easily forget that the software being used is an evaluation version and has not been purchased.

Back to top >>


ComponentOne has a licensing model based on the standard set by Microsoft, which works with all types of components. The licensing model is per developer, or per any machine that needs to build the application.

When a user decides to purchase a product, they receive a serial key. The serial key must be activated on the user's development machine (and up to two more machines, such as a laptop and build machine) in order to properly license any app built with ComponentOne controls.

When the user fully installs any product from the GrapeCity website, the licensing tools needed to activate the serial key will be installed. The user will be prompted to activate their serial key during the build process once their 30-day trial has expired.

When a licensed component is added to a .NET Framework form or page, Visual Studio obtains version and licensing information from the newly created component and will generate a licenses.licx file and add it to the project. The licenses.licx file contains the licensed component strong name and version information. The GrapeCity Visual Studio plugin (Under Tools) can be used to update this file and help resolve licensing issues.

When queried by Visual Studio, the .NET Framework component looks for licensing information stored in the system and generates an assembly resource file which contains the actual runtime license. For a Web Forms application, the run-time license may also be stored as an embedded resource in the App_Licenses.dll assembly, which must always be deployed with the application.

Later, when the component is created at run time, it obtains the run-time license from the appropriate assembly resource that was created at design time and can decide whether to simply accept the run-time license, to throw an exception and fail altogether, or to display some information reminding the user that the software has not been licensed.

When building .NET Core, Xamarin and UWP applications, the licensing is completely handled at build time. When queried by the NuGet build scripts, the component looks for licensing information stored in the system and generates a unique GrapeCity runtime license. If the license is valid, the component will generate a .gclicx file and include it with the build output. Only one .gclicx file is generated per application build. This file is not added to the project - it's only generated and distributed with the application output.

All ComponentOne Editions are designed to display licensing information if the product is not licensed. Applications will not run correctly if the license is missing or invalid after the 30-day trial has expired.

Back to top >>


The following topics describe some of the licensing scenarios you may encounter.

Back to top >>


We try very hard to make the licensing mechanism as unobtrusive as possible, but problems may occur for a number of reasons. Here are the most common problems and their solutions.

Back to top >>


Q: How is ComponentOne Studio Enterprise licensed?

A: ComponentOne Studio and its Editions are licensed per developer per seat. This includes anyone who uses ComponentOne Studio components and controls to create and compile projects in Microsoft's Visual Studio. If someone wants to work with the code that a component or control has created, they need to have a license.

There are no limits on the distribution of applications—unlimited, royalty-free, run-time distribution. The licensing only affects design time.

Q: What is the difference between the Subscription and the License?

A: When you purchase the license, you receive a free one-year subscription that entitles you to the latest version of the software. The license is perpetual and does not expire; the subscription runs year to year. If you choose not to renew, you can still use the software as is; you just won't have access to the latest version.

Q: What is activation?

A: Activation is used by GrapeCity to verify the authenticity of the product key used to license the software and also to ensure that keys are only used to license an approved number of machines. The activation process does not collect any customer-specific information and protects the end user's privacy completely.

Q: Since I have a new (19-digit) license key, how do I use an older version of any ComponentOne product?

A: If you have a new 19-digit license key it must first be activated through the GrapeCity License Manager tool. Then if you'd like to use an older version of any ComponentOne product (version prior to 2020 v2), you can launch the legacy C1LicenseActivation tool and it will prompt you to install an old key that matches the new key's subscription time period. Then you will be able to use old versions of any product licensed within your subscription.

If you have a 28-digit license key you can use just the first 17 digits of your serial number to unlock older products through C1LicenseActivation. For example, for SE307AC-3G-XXXXXX-06-6WNWR1K you would use SE307AC-3G-XXXXXX.

Q: What is the difference in the serial numbers?

A: Beginning July 29th, 2020, GrapeCity distributes serial keys that are 19 characters long. These new keys are compatible with the GrapeCity License Manager activation tool. The old ComponentOne serial keys are 28 or 17 characters and are compatible with the C1LicenseActivation tool. The new serial keys can still be used with older versions of ComponentOne products, and vice versa, so long as you use the correct activation tool for the serial key you are trying to activate.

Q: Can I still license new controls with an old serial number?

A: Yes. As long as your serial number reflects an active subscription, you can enter it into the C1LicenseActivation tool and successfully license your controls.

Q: I have a serial key between 2019 v2 and 2020 v1, will I need a new serial key to update 2020 v2?

A: No. You can continue to use all future versions within your subscription without issue. The controls will first check for a new license, and if one is not found, they will check for a valid old license. The serial key would still need activated on the developer's machine using C1LicenseActivation if it was purchased before July 29th, 2020.

Q: When I tried to activate my serial key, I get a message like "Hit Machine Count Limit", how can I request additional activations?

A: The usage of this serial key has been exceed the limit. Please try to deactivate it on a different machine, which does not need it any more, and then try to activate it on this machine again. If the problem still occur, please visit and submit a re-activation request, we will handle with your request soon.

Q: When I tried to activate my serial key, I get a message like "Hit Frequency Limit", how can I activate my license?

A: The serial key has been activated too frequently. A serial key can only be deactivated and reactivated up to 9 times within 24 hours. Please try it after 24 hours. If the problem still occur, please visit and submit a re-activation request, we will handle with your request soon.

Q: I received an error that my serial number is invalid. What should I do?

A: 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). If you're still experiencing problems, please contact your sales representative for assistance. The GrapeCity Sales team can be reached at 1-800-858-2739. Your sales representative can determine if your serial number is valid and help you to get a valid serial number or further assistance if your serial number is valid.

Q: I have an expired license on my machine and my controls did not activate properly. What do I do?

A: Run the license removal tool. Files are located here. This removes the existing license. Once this is done, you can activate your studio by pressing the Activate button in the About Box of any ComponentOne Studio control.

Q: The license removal tool did not find any licenses. What do I do next?

A: You will need to manually deactivate your controls. To do this, go into the About box of any .NET 2.0 control, and click deactivate. Enter your new license key into the appropriate boxes and click OK.

Q: Is there a limit to the number of activations I can use for a single license?

A: The limit is three (3) machines per license. Allowed installations include any combination of a primary machine (desktop), backup machine (laptop), build machine, or test machine.

Q: Is any personal information collected/submitted during the activation process?

A: No. No personal information is collected.

Q: What happens if I have used all of the activations I am allowed and I need to activate another computer?

A: You can deactivate on one machine in order to free up an activation for a different machine. A serial key can only be activated on 3 different machines and up to 9 times within 24 hours. If you cannot deactivate any of your current computers, you will need to purchase additional licenses or request an additional activation. You may request an additional activation from the following site, by clicking Reactivation:

Q: I was previously given a multi-year license, what do I do now?

A: You'll need to receive a new license key. Please contact your sales representative for assistance. The GrapeCity Developer Tools sales team can be reached at 1-800-858-2739.

Q: I want to activate products on a machine that does not have an internet connection. What do I do?

A: You can activate an offline machine through another machine that is connected to the internet. This is known as offline activation.

If you have a new key purchased or renewed after July 29th, 2020, you can activate an offline machine from the following site, by clicking Activation (or Deactivation for offline deactivation):

If your key is from before July 29th, 2020, you can activate by phone, e-mail, or online. All three processes are described here: Once you've completed your manual activation, you'll receive an Activation Code. Enter the serial number of your product and the authentication number you received into the Activation Wizard, and complete the process.

Q: If I am redistributing ComponentOne Studio controls in my application, do my users need to use activation?

A: No. Only the developers who are installing ComponentOne Studio controls for use in development projects need to activate their controls.

Q: What is the impact of activation on UAC (User Account Control)?

A: Licensing procedures invoked by ComponentOne Studio setups will always request activation so that all controls will be licensed. Running the ComponentOne Studio setup will require Administrative privileges during execution. For Windows Vista operating systems and higher, a prompt requesting Administrative privileges will be given if the Vista UAC is turned on and the process starting the setup program does not already have Administrative privileges.

Back to top >>

ActiveX Edition Licensing

ActiveX Edition licensing is handled transparently by .NET in C#.NET and VB.NET, so special consideration is not required when adding ActiveX controls to a form or user control in .NET. However, if you put an unlicensed version of the control on a form, or you wish to change licenses, you must remove the old control and add it back again to get the new licensing. The behavior is identical to that of a VC++ project using an ActiveX control.

For information on dynamically adding ActiveX controls that require run-time licenses, see the Microsoft Support site. All ComponentOne Studio Editions are designed to display licensing information if the product is not licensed. None will throw licensing exceptions and prevent applications from running.

Back to top >>

ComponentOne Studio Enterprise for Xamarin Licensing

Xamarin apps require an app key to work. Generate an app key now.

Back to top >>

ASP.NET MVC Edition Licensing

ASP.NET MVC and Web API apps require an app key to work. Generate an app key now.

Back to top >>

UWP Edition Licensing

UWP apps require an app key to work. Generate an app key now.

Back to top >>

Silverlight Edition Licensing

  1. Once the license is activated on the machine, open the Silverlight project(s).
  2. Remove the attribute c1:C1NagScreen.Nag="True" from the XAML markup of each C1 control.
  3. Rebuild the application.

Back to top >>

LightSwitch Edition Licensing

  1. After licensing the machine, open the LightSwitch project(s).
  2. Open the screen(s) containing C1 controls.
  3. Select the C1 control node (eg. C1FlexGrid node).
  4. Save the screen.
  5. In the Properties window, you should see a green shield icon next to the About C1FlexGrid link. This needs to be done for each screen that contains a C1 control.

Back to top >>

WinRT Edition Licensing

The licensing for WinRT is similar to Silverlight.

  1. Once the license is activated on the machine, Open the WinRT project(s).
  2. Remove the attribute Xaml:C1NagScreen.Nag="True" from the XAML markup of each C1 control.
  3. Rebuild the application.

Back to top >>

Source Code Licensing

Full source code for any ComponentOne (C1) product is available upon request. C1's source code is purchased to be used as a reference or with rights to modify and redistribute. In both cases, the source code license is purchased in addition to standard developer licenses following guidelines set by our EULA.

ComponentOne Source Code License Include

  • Full source code for one product includes all components belonging to a single platform version/single .NET version
  • Enterprise controls are included for the platforms in which they are supported
  • Discounts are available to purchase additional products, versions, or updates
  • We support you to ensure you can access and build the source code. Once the source code is modified, we cannot guarantee further support

Different Types of Source Code Licenses

For Education & Reference - You may receive the source code for reference purposes to help with education and debugging. However, this does not give you the right to modify and redistribute a custom version of the controls. The price for this license is significantly less than the license to modify and redistribute the source code.

For Modification - Modify the source code and redistribute the modified components within your application. This license does not entitle you to redistribute the components for third-party use. This license's benefit is that you may modify the controls to add missing features that your application requires or customize the control beyond the standard licensed version. The modified component must keep the GrapeCity copyright intact, and you may not create a new assembly and resell it (known as white label software). The price for this license type is significantly more than the education & reference price.

Contact Us for pricing information.

Back to top >>