This version makes a number of minor updates across the WPF control product line. A new TreeListView sample shows how to sort columns when their header is clicked, various UI automation improvements were made, and numerous Bars enhancements were implemented.
See the related announcement post for the detailed list of enhancements and updates.
While this major new version focuses on the introduction of the new Bars product beta, it also has a number of other minor updates across other products that are described in the related announcement post, which contains a detailed list of enhancements and updates.
Here's a look at some of the new features.
v23.1 takes the wraps off a new Bars product that implements advanced fluent ribbons, toolbars, menus, and related controls.
The new fluent Ribbon has the latest Office appearance and includes the use of subtle animations throughout all controls.
Ribbon can instantly switch between Classic (taller) and Simplified (single-row) layout modes, allowing for configuration of the variant resizing behavior in both modes.
Complex galleries can appear in the Ribbon, as well as in any popup and context menu. It's simple to create new galleries with rich visualizations for any need.
The StandaloneToolBar control can alternatively be used as an app's primary toolbar, or alternatively within tool windows. It can host any control that can be used in Ribbon and overflows items to a popup as needed.
Three user interface density options can be chosen, letting your application select whether to better support a large number of controls, or focus more on touch-friendliness.
The entire control hierarchy can be built using MVVM (preferred), or alternatively directly in XAML. An optional open source MVVM library is available that makes it easy to configure the Bars controls with MVVM techniques. In fact, the main Ribbon demo seen in earlier screenshots above is completely constructed from code-behind view models!
Since .NET 5 is now out of support by Microsoft, we updated our .NET 5 targets to .NET 6. .NET 5-based apps can still use .NET Core 3.1 targets.
We’ve also moved our .NET Framework target to use 4.6.2 minimum, as it’s the most recent supported version of .NET Framework.
Finally, we now automatically code sign all our assemblies instead of shipping both non-signed and signed variations.
This version makes a number of minor updates across the WPF control product line.
See the related announcement post for the detailed list of enhancements and updates.
Bill Henning (Actipro)
This version makes a number of SyntaxEditor improvements, and also fixes a bug introduced in v23.1.0 when parsing image data on certain machines. Several NuGet packages have been updated to better support cross-platform usage.
See the related announcement post for the detailed list of enhancements and updates.
This version contains updates across all our WinForms controls to support high DPI environments and add new dark color schemes. .NET version compatibility was modernized to the latest supported .NET versions, and a large number of other various feature additions and bug fixes were made to all products.
See the related announcement post for the detailed list of enhancements and updates.
Here's a look at some of the new features.
Historically, high DPI support in WinForms has been a mixed bag. Newer Windows API’s and recent updates to .NET have greatly improved the scenario, but high DPI support is still not free and developers must put in the effort to ensure proper DPI awareness.
With our WinForms Controls v23.1 updates, we’ve done our part to make sure our controls can render correctly in high DPI environments. Some of the changes include:
NOTE: Anyone with a DPI-aware application needs to read our v23.1 conversion topic and thoroughly test. It could be that you were already compensating for lack of DPI-awareness that we now handle, so you don't want to do something like scale our controls if we're already scaling them (causing double scaling).
We’ve also revamped how all renderers determine which colors are being used so we can better support a dark color scheme. New “Metro Dark” renderers are available for all our products and can be used to better integrate with dark-themed applications.
In regards to .NET version compatibility, we have: