Skip to main content Skip to footer

How to Update ComponentOne Controls

So you’ve already downloaded ComponentOne controls, but now you want to update to the latest version. We’ve made it possible to update the controls in several different ways, so it might seem complicated for new users. This article breaks down each option so you can choose your preferred approach. You might even learn something new that improves your dev cycle.

There are two main ways to update the controls:

  1. Using NuGet packages from
  2. Using the C1ControlPanel application

Using NuGet Packages from

NuGet is the official .NET package manager for distributing .NET libraries. We publish all active ComponentOne control libraries to for your convenience. You can download and update our control libraries in Visual Studio through the NuGet Package Manager under the Tools menu.

Why choose NuGet: If your application uses NuGet packages and you need to get the latest version (or any version) with no samples or tools, this is the fastest and easiest way to update the controls.

When you use NuGet packages, the updating happens directly to your project, so you are ready to build with the updated version immediately.

Why NOT to choose NuGet: If your ComponentOne subscription is not current, you might inadvertently update a package beyond your license. For example, when you purchase 2023 v1 (, your license allows you to update to 2024 v1 ( without issue. To get updates beyond that, you must renew your license. The Visual Studio NuGet package manager does not support licensing checks.

You can still use NuGet and avoid licensing issues if you set up a local NuGet source. There’s more on that at the bottom of this article.

Using the C1ControlPanel Application

The C1ControlPanel is our web installer application that you should use to first download and install any ComponentOne Edition. This installer gives you the control libraries (DLLs) and local NuGet packages, samples, and essential tools and applications. It installs the libraries/assemblies to a single location on your computer that your Visual Studio projects can reference.

You can also use the C1ControlPanel to get new updates. By doing so, the C1ControlPanel will simply update the files at their installed location.

Steps to updating through the C1ControlPanel:

1. Download and launch the C1ControlPanel web installer from

TIP: If you downloaded the C1ControlPanel previously, you can just relaunch it. It will automatically check for available updates.

Download ComponentOne

2. Locate the .NET platform tile you wish to update and select the desired version from the drop-down.

WinForms Edition

3. Check the boxes on the right to indicate which .NET versions you want to update. You can also choose to update and get the latest samples here.

4. Click Proceed to complete the update installation.

Alternative Approach: Download a ZIP Containing the Controls

When you update following the steps above, the C1ControlPanel will fully install and update all samples and tools as well. Some users prefer to download a clean zip file that contains the control DLLs only that they can swap out in their application. The C1ControlPanel supports this as well through the Build Repository tab.

  1. Click on the Build Repository tab.
  2. Expand the product you wish to update and locate the .NET version.
  3. Click the Update or Download button.
  4. Select the Latest Version, Latest Licensed Version, or any specific version from the drop-down.
  5. Click Download Zip.

Then, you can unzip the file and replace the controls at their installed location under C:\Program Files (x86)\ComponentOne. Note that this is an alternative approach and is not required.


How to Update Visual Studio Projects

After downloading the update through C1ControlPanel, you may need to update your project references since the C1ControlPanel only updates the control libraries at their installed location.

If you are referencing the control libraries directly (via Toolbox or Add Reference), then the update process is as follows:

  1. Set the Specific Version property to False. In Visual Studio, select the reference from the Solution Explorer and set its Specific Version property to False. This forces Visual Studio to always use the latest installed version. You typically only have to do this one time and not again on future updates.
  2. Remove version-specific information from the Licenses.licx file. If you’re working with .NET Framework, Visual Studio loves to add very specific version information to the Licenses.licx file. This can be removed at any time, but it must be removed when you update the referenced version. To clean the Licenses.licx file, select Tools | GrapeCity | Update Projects | Add missing entries to the licx file. Or, you can simply remove everything on each line after and including the second comma.


If you are or would like to reference the packages by NuGet locally (and not from, you can read the final section below.

How to Create a Local NuGet Package Source for ComponentOne

By setting up your own local source, you can be sure not to exceed your ComponentOne subscription. Plus, if your company requires full control over which packages their team can access and update, this might be a good solution. We install the NuGet packages for most Editions to C:\Program Files (x86)\ComponentOne\Packages. These packages get updated when you install the update following the C1ControlPanel steps above (Note: they are not included in the ZIP option). These can then be used to set up your own local NuGet package source.

To create a local NuGet package source, open Tools | NuGet Package Manager | Package Manager Settings. Select Package Sources and click the green “+” button to add a source that points to the install location I mentioned above. Read How to Manage ComponentOne Packages Using Nuget for more information.

Once you are referencing the control libraries by a local NuGet source, you can then update each package separately through the NuGet Package Manager at any time (Tools | Nuget Package Manager | Manage NuGet Packages for Solution…).

Ready to Get Started? Download ComponentOne Today!

comments powered by Disqus