2019 v3 is here with .NET Core 3.0, new Ribbon, FlexGrid Detail Row, and more!

Posted by: greg.lutz on 20 November 2019, 7:39 am EST

  • Posted 20 November 2019, 7:39 am EST

    See the full details here
    https://www.grapecity.com/blogs/new-release-componentone-2019v3
    Download the latest version through the C1ControlPanel
    https://www.grapecity.com/en/download/componentone-studio
  • Replied 21 November 2019, 4:20 pm EST

    Hello Greg,

    Could you please share with us the link for offline installer as well?

    Thanks,
    Gevorg
  • Replied 22 November 2019, 6:33 am EST

    Hello Gevorg,

    Here is the offline installer
    https://cdn.grapecity.com/ComponentOne/2019v3/C1Studios_20193.1.3.exe

    We still do recommend anyone to use the C1ControlPanel, because it has access to more samples and products, and the offline installer may not work once the control panel has installed any of the same products.

    Regards,
    Greg Lutz
  • Replied 7 January 2020, 4:45 am EST

    Hi,

    the background for my question is, I am building a .NET Core 3.1 windows forms application, and using ComponentOne latest edition for winforms.

    There are few windows forms controls become obsolete with .NET Core 3.1. Please find below link, for more information.
    https://docs.microsoft.com/en-us/dotnet/core/compatibility/winforms

    For example ‘ContextMenu’ control is obsolete in .NET Core 3.1 and the better version is ContextMenuStrip, so I have replaced the occurrences of ContextMenu in my application with ContextMenuStrip control, and its working fine.

    But, Looks like even in the latest component one winforms edition, the control C1.Win.C1Command.C1ContextMenu which is still using the obsolete ContextMenu system.windows.forms control, and because of this I am getting below error message, at run-time. 'could not load type system.windows.Forms.ContextMenu.


  • Replied 7 January 2020, 5:54 pm EST

    Hi,

    Thank you for reporting it. I have forwarded your concern to the developers [ID: 415766].
    I will get back to you once we have some information.

    Regards,
    Ruchir
  • Replied 12 January 2020, 7:33 pm EST

    Hi,

    This is just an update that the team has confirmed the bug and the issue shall be fixed in one of the future releases.
    We will once again update you when the issue is fixed.

    Thanks,
    Ruchir
Need extra support?

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

Learn More

Forum Channels