Component One Version Confirmation

Component One Version Confirmation

Posted by: mdynna on 15 June 2026, 1:46 pm EST

• 

  mdynna

  • Post Options:
  • Link
    Copy

  Posted 15 June 2026, 1:46 pm EST

  Hi there, we have just updated to WinForms 2026 v1. Our applications are targeting .NET Framework 4.8. There seems to be two versions of every assembly in NuGet, so I’d like to confirm that we should be using all the versions that start with 4.8? For example: C1.Win.C1FlexGrid 4.8.20251.721.

  These assemblies maintain the “C1” prefixes in the assembly namespaces (contrary to documentation) so I wanted to make sure we are using the correct ones.

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 16 June 2026, 2:25 am EST

  Hello,
  
  To clear up the confusion regarding the package versions, here is the explanation of the two different versions you are seeing in NuGet:
  
  Introduction of Multi-Target Packages: Starting from our 2025v2(740) release, we transitioned to multi-targeted packages. This means that a single NuGet package now serves multiple target environments (both .NET and .NET Framework). When you add this package to your project, it will automatically detect your project’s target framework and use the relevant DLLs. These packages are named with C1.Win.* naming format.
  
  Note: Due to this transition, we have also updated our DLL names and namespaces. For example, earlier the DLL name for the C1FlexGrid control was C1.Win.C1FlexGrid.x.x.dll, and the namespace was C1.Win.C1FlexGrid. After the update, they have changed to C1.Win.FlexGrid.x.x.dll and C1.Win.FlexGrid, respectively. Therefore, if your existing code still uses the older names, you will need to update them. You can do this easily using Visual Studio’s Find and Replace feature.
  
  Legacy Packages are no longer updated: The packages using the C1.Win.C1* naming format are our older, framework-specific packages. Most of these have been discontinued, and the new versions will only be released in our multi-targeted packages like C1.Win.*
  
  For your WinForms 2026v1 upgrade, please use the latest multi-targeted packages. They will fully support your .NET Framework 4.8 application while ensuring you get the latest updates.
  
  If you have any confusion, you can let us know the C1 controls you currently use in your project, and we will let you know the relevant NuGet packages you need to install.
  
  Regards,
  
  Uttkarsh.

• 

  mdynna

  • Post Options:
  • Link
    Copy

  Posted 22 June 2026, 12:01 pm EST - Updated 22 June 2026, 12:07 pm EST

  Ok, everything is working except for the C1 Editor. Referencing the C1.Win.Editor (version 10) assembly creates many breaking changes.

  I see the Samples provided for .NET Framework 4.8 reference C1.Win.C1Editor (version 4.8) mixed with version 10 of other assemblies. This seems a bit odd, so I wanted to confirm that we should also be referencing version 10 assemblies except for C1Editor.

  

  1199×383 36.3 KB

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 23 June 2026, 3:22 am EST

  Hello,
  
  Please note that most ComponentOne controls have transitioned to a unified, multi-targeted package architecture starting from the 2025v2(740) release.
  
  However, a few controls, such as C1Editor or C1Input, rely on a different codebase than their .NET Core counterpart. So, these specific packages continue to be maintained and updated as separate packages. This ensures that customers with existing applications can upgrade without being forced to have massive breaking changes or extensive code rewrites.
  
  To answer your question - yes, you can use the 10.0 packages for all controls except C1Editor, which should continue to use the 4.8 package. Therefore, installing both packages, as shown in your screenshot, is a supported configuration and should work correctly.
  
  We hope this clarifies your doubt. If you have any other concerns, feel free to ask.
  
  Regards,
  
  Uttkarsh.