News

GrapeCity ComponentOne 2021 v3 Supports .NET 6, VS 2022 and WinUI

Development toolmaker GrapeCity issued the year's final update to its ComponentOne toolkit of UI controls, adding new features for Microsoft's new .NET 6 and Visual Studio 2022 milestone releases.

The new release, called ComponentOne 2021 v3, also graduated from beta its WinUI edition, supporting Microsoft's now-decoupled native UI platform component-- serving as the company's next-gen UI library for creating Windows apps -- that ships with the Windows App SDK (formerly called "Project Reunion").

But it's the support for VS 2022 -- the first 64-bit edition of the IDE -- and the unifying .NET 6 framework that leads the update.

"Microsoft has given .NET developers a true gift with the new, optimized development platform that bridges the gap between old and new—unifying the once complicated and uneven .NET family of frameworks," said the company in a Dec. 8 blog post.

"We have migrated all .NET 5 controls to .NET 6 and released .NET 6 versions of TrueDbGrid, GanttView, FontPicker, and Scheduler. The Print Preview family of controls (C1PrintDocument and C1PrintPreviewControl) are now out of beta. .NET 6 is the first LTS (long-term support) platform in Microsoft's larger plan. With that comes at least three years of support. Visual Studio 2022 support includes toolbox, Tools add-on, and limited design-time support. The controls have been tested to work on the design surface, but not all designers from .NET Framework are supported in .NET 6."

The update also enhances Blazor functionality, notable because Microsoft actually mentions GrapeCity and other third-party tooling vendors as being "top component vendors" in its Blazor documentation.

New DataFilter Component for Blazor
[Click on image for larger view.] New DataFilter Component for Blazor (source: GrapeCity).

"For Blazor 2021 v3, we are shipping two versions: .NET Core 3.1 and .NET 6. The benefit of switching to .NET 6 is that you will no longer need to manually add the references to scripts and JavaScript files for each control library. Enjoy the intrinsic benefits that .NET 6 brings to Blazor, such as faster loading of WebAssembly applications," GrapeCity said.

"In this release, we focused on adding drag-and-drop functionality across the Blazor suite of controls -- ensuring the client-side behavior works well in both server and WebAssembly applications. We incorporated cross-platform DataFilter UI in Blazor for advanced Blazor datagrid and list view filtering."

Other improvements, updates and enhancements were listed for WinForms, WPF, ASP.NET MVC and other components.

More about the update is available at the ComponentOne web site.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube