Migration to .NET 6

Posted by: info on 28 December 2021, 8:20 pm EST

  • Posted 28 December 2021, 8:20 pm EST

    Hello, we are doing some migration tests to .NET 6 but some components have not been converted, such as C1Sizer or C1Editor.
    Will they be developed? Is there a date?

    For the truedbgrid there is a beta version, but none of these components.

    Regards, Marco
  • Replied 29 December 2021, 6:36 pm EST

    Hello Marco,

    As per the developers, the C1Sizer and C1Editor both the controls are in the plans to include in .NET 6 in 2022 but there is no specific ETA available yet/

    Prabhat Sharma.
  • Replied 1 April 2022, 12:22 pm EST

    Hello, any news or date on which the C1Sizer component will be available in .NET 6? Please let me know as I urgently need to know if I can wait or should I use a different control. Thanks, Regards, Marco.
  • Replied 3 April 2022, 8:14 pm EST


    As per the development team the Sizer control will be ported to .NET 6 in the next public release 2022v2.

    Prabhat Sharma.
  • Replied 7 April 2022, 2:31 am EST

    I've noticed for e.g. the C1TextBox the (old) properties DataSource and DataType are missing, meaning the .NET 5/6 version of this important control is not backwards compatible with any .NET 4.x Framework code that needs migration.

    Will this always require manual conversion of any code; or will these properties be supported at any stage in the future?
  • Replied 7 April 2022, 9:27 pm EST

    Hello Abraham,

    Both the mentioned properties DataSource and DataType are available in the .NET 5 and .NET 6 both the C1TextBox control. Please see the attached screenshot for reference.

    If you are using any issue in migrating your application in .NET 5/.NET 6 then please let us know.

    Prabhat Sharma.

  • Replied 9 April 2022, 6:13 am EST

    @Prabhat Sharma, that's great, then their existence is just missing from the documentation :-) Maybe good to add that to avoid confusion.

    The only doc page I can find is this one which doesn't have the two properties mentioned:


    Is there a more up-to-date API doc page for the .NET 6 version?
  • Replied 10 April 2022, 10:29 pm EST

    Hello Abraham,

    Apologies for the inconvenience.
    Please find the correct documentation link for the Input .NET 6 API.

    I will ask the concerned team to get it updated on the website soon.

    Prabhat Sharma.
  • Replied 10 April 2022, 11:54 pm EST

    @Prabhat Sharma: thanks, that certainly provides clarity; looking forward to the updated online docs to avoid confusion for others.
  • Replied 17 April 2022, 4:55 am EST

    We have older .NET 4.8 projects using the C1 suite 2015 version; can we install the latest NET 6 version of the C1 suite on the same machine for NET 6 to allow migration without breaking things?
  • Replied 18 April 2022, 3:36 pm EST


    To work with the .NET 6 controls you needs to install the Visual Studio 2022 in your machine.
    You can install the .NET 6 controls directly via NuGet Package Manager with installing complete suite.
    Please see the FlexGrid documentation link demonstrating the same:

    Note: Please make sure you have latest version license to work with the .NET 6 controls.

    Prabhat Sharma.
  • Replied 20 April 2022, 8:00 pm EST

    is there a beta version of the c1sizer component available in .NET6 so you can start porting it while you stabilize it?
    Regards, Marco
  • Replied 24 April 2022, 9:55 pm EST

    Hello Marco,

    The C1Sizer in .NET6 is planned for the 2022V2 release of ComponentOne.
    The ETA is at the end of July 2022.
    We will update the thread once it is released.

    Prabhat Sharma.
  • Replied 3 May 2022, 2:11 am EST

    @Prabhat Sharma: Doing testing/evaluation I just noticed the .NET 6 version of the C1Label control is missing the DataSource / DataMember properties (while e.g. C1TextBox / C1DbNavigator / C1TrueDbGrid indeed do have these); this will cause conflicts when converting projects from .NET 4.8 to .NET 6; is there any reason why these properties have been removed? Will they be added still in the future?

    What is the recommended replacement for the .NET 4.8 C1DateEdit control? There is no such control in the .NET 6 suite it seems.

    Testing the C1TrueDbGrid (v6) I can't find a way to access the grid designer that allows for definition of columns/display/format etc. In .NET 4.8 the VS property window would show the various commands for this control like 'Design ..', 'Save lay-out', The control's available tasks are only 'About C1TrueDbGrid' and 'Dock in Parent Container'. Am I missing something?

    Some behaviour with these properties in the VS Winforms designer is inconsistent: e.g. for C1TextBox I can set the DataSource via the property window to a BindingSource control (that has no DataSource yet) present on the Form . But for the C1DbNavigator and the C1TrueDbGrid control I can't do that with the designer, but only via code. It would seem logical for the C1DbNavigator and the C1TrueDbGrid controls to support the same definition flexibility as the C1TextBox has in this regard.
  • Replied 3 May 2022, 9:38 pm EST

    Hello Abraham,

    We too can observe that the DataSource property is not present for C1Label and we are discussing this with the developers. For now, you can use the Add method of the DataBindings property to bind the C1Label with the data source.

    For using the C1DateEdit control in .NET 6, you can use the following package:

    The complete designer support has not been implemented yet for our .NET 6 controls due to some limitations but it is in our plans to add them in the future.
    [Internal Tracking Id: C1WIN-27317]

    Prabhat Sharma.
  • Replied 4 May 2022, 4:52 am EST

    @Prabhat Sharma: Thanks for the C1.Win.Calendar C1DateEdit hint. Testing that one I noticed it is not possible to make the control use the Current Culture settings of the machine it is running on using the designer/properties window. Neither can I change the culture from 'en-US' to anything else using the designer/properties window. I think this is a bug.

    By code I can set the control's CultureInfo to the CurrentInfo.CurrentCulture, and thus let the control honour any local system settings for date formats etc,. The 'old' .NET 4 C1DateEdit control did all this by default (using the system culture settings) - which is the expected behaviour.

    Would be great if the devs could:
    - fix this C1DateEdit CultureInfo behaviour bug
    - make C1Label consistent with other controls and support DataSource/DataMember
    - make C1DbNavigator + C1TrueDbGrid consistent with e.g. C1TextBox and allow the DataSource property to be set to any BindingSource control on the form with the designer/properties window.
    - provide full designer for C1TrueDbGrid

    Thanks for replying and relaying this info to the devs team!
  • Replied 4 May 2022, 7:18 pm EST

    Hello Abraham,

    1: fix this C1DateEdit CultureInfo behavior bug.
    This is already reported and will get fixed in the next 2022V1 hotfix release.

    2: make C1Label consistent with other controls and support DataSource/DataMember.
    The developers have this in their plans and will add these properties in future.

    3: make C1DbNavigator + C1TrueDbGrid consistent with e.g. C1TextBox and allow the DataSource property to be set to any BindingSource control on the form with the designer/properties window.
    As per the developers, it seems to be a bug. We will let you know as soon as we get the update from the developers.

    4: provide full designer for C1TrueDbGrid
    We have requested the developers for the same and will update you on this as soon as we get the updates.

    Prabhat Sharma.
  • Replied 4 May 2022, 7:49 pm EST

    @Prabhat Sharma: that sounds good, we've got big projects using C1 Winforms components to convert from .NET 4.8 to .NET 6, but that can only happen once the APIs/behaviour are nearly identical and manual code adjustment requirements are minimal. Looking forward to any updates .. !
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels