Use the WinForms Migration Utility to update your .NET Framework applications to the latest version of the ComponentOne WinForms libraries. The utility automatically handles the package and namespace changes introduced in 2025 v2 (build 20252.740).
Download: WinForms Migration Utility
Who Should Use This Utility?
Use this utility if:
You have a Windows Forms application targeting .NET Framework 4.x. and you want to upgrade your ComponentOne WinForms controls to 2025 v2 (20252.755) or later.
Note:
-
You can also use the utility to update existing .NET 8, 9, 10+ applications to the latest version, however the utility does nothing more than update the nuget packages since there are no namespace changes.
-
The utility only updates ComponentOne packages and namespace references throughout your project source code. It does not update your project’s .NET build or target version.
Background - Why This Utility Exists?
Beginning with 2025 v2 (build 20252.740), ComponentOne WinForms packages for .NET Framework were consolidated with the corresponding .NET packages designed for .NET 5 and later. This consolidation uses a multi-targeting approach, allowing a single package to support multiple .NET platforms while providing a consistent API and namespace structure.
As part of this change, package names and namespaces were updated to align with our modern naming conventions. For example:
-
(Previous format > New format)
-
C1.Win.C1Command > C1.Win.Command
-
C1.Win.C1FlexGrid > C1.Win.FlexGrid
-
C1.Win.C1GanttView > C1.Win.GanttView
-
C1.Win.C1Gauge > C1.Win.Gauge
- C1.Win.C1Input > C1.Win.Input
-
C1.Win.C1InputPanel > C1.Win.InputPanel
-
C1.Win.C1List > C1.Win.List
-
C1.Win.C1Schedule > C1.Win.Schedule
-
C1.Win.C1Sizer > C1.Win.Sizer
-
C1.Win.C1SpellChecker > C1.Win.SpellChecker
-
C1.Win.C1SplitContainer > C1.Win.SplitContainer
-
C1.Win.C1SuperTooltip > C1.Win.SuperTooltip
-
C1.Win.C1Themes > C1.Win.Themes
-
C1.Win.C1Tile > C1.Win.Tile
-
C1.Win.C1TouchToolkit > C1.Win.TouchToolkit
-
C1.Win.C1TrueDBGrid > C1.Win.TrueDBGrid
The new packages support:
-
.NET Framework 4.8
-
.NET 8
-
.NET 9
-
.NET 10
-
Future supported .NET releases
This means the same NuGet package can now be used across both .NET Framework and modern .NET applications.
What Needs to Be Updated?
If your application references any libraries that were renamed as part of this transition, you must:
-
Replace the old NuGet package references with the new package names.
-
Update any corresponding namespaces throughout your project.
After you perform step 1, you may see error messages such as: The type or namespace name ‘C1FlexGrid’ does not exist in the namespace ‘C1.Win’ (are you missing an assembly reference?)
You can fix this manually by replacing ‘C1FlexGrid’ with ‘FlexGrid’. But if you have large projects, this can be a tedious task.
The WinForms Migration Utility automates both tasks, allowing you to migrate existing projects with minimal manual effort.
How to Use the Migration Utility
-
Download and unzip the migration utility project.
-
Launch Visual Studio and open the C1WinFormsMigrationUtility.sln
-
Build and run the project
-
Click Browse… to locate the folder containing your project source
-
(Optional) Check the box to Create a backup before migration
- Select the Target Version. In most cases you should choose the latest version but this utlity supports updating to any version released after 20252.740.
-
(Optional) Click Analyze to get a preview of what will be updated. This will list the number of source code files, LICX files, RESX files and package references that will be updated. For more details on how the migration utility works, check out the readme.md file included in the zip.
-
Click Migrate to perform the migration.
