Why this update matters
- Conflict-free composition: Mix Toolkit and Xceed DataGrid in the same solution without brittle workarounds.
- Faster theming with less XAML: AppearanceProperties and new converters give you clean, centralized control over radius, spacing, and typography.
- Predictable editing UX: RichTextBoxFormatBar can stay visible and be precisely positioned.
- Friendlier filtering: New dependency properties improve discoverability and control.
What’s new in Xceed Toolkit Plus for WPF 5.1
- Conflict‑free mixing of Toolkit and Xceed DataGrid
- What changed: Xceed.Wpf.DataGrid.dll is now Xceed.Wpf.DataGrid.Toolkit.dll.
- What it solves: You can run Toolkit and full DataGrid side-by-side without assembly conflicts—ideal for modular apps and gradual migrations.
- Migration checklist:
- Update package/reference to Xceed.Wpf.DataGrid.Toolkit.dll
- Adjust assembly-qualified XAML namespaces if you used them
- Verify binding redirects and any build-copy steps
- Rebuild and smoke-test views using both Toolkit and DataGrid
- Easier, consistent styling with AppearanceProperties
- The challenge: Many controls didn’t expose radius, margin, foreground, or font weight—forcing template edits.
- The solution: AppearanceProperties centralizes these for a consistent theme:
- Radius
- Margin
- Foreground
- FontWeight
- Benefits:
- Less template surgery and duplicated styles
- Consistent radius scale (e.g., 2/4/6/8) across inputs, lists, and panels
- Cleaner resource dictionaries and faster theme updates
- Converters for rounded, modern UI
- CornerRadiusToUnderlineMarginConverter: Aligns underline margins so they don’t collide with rounded edges.
- CornerRadiusReplacementConverter: Normalizes child radii to match parent containers.
- Where this shines:
- TextBox underlines inside rounded cards
- Popups and menus within rounded containers
- List/Tree items that should inherit parent curvature
- RichTextBoxFormatBar that stays put
- Always-visible option: Keep the format bar present for power users.
- Precise placement: Use Position and the FormatBarPosition enum to anchor it where it belongs (top, bottom, dedicated region).
- Outcome: Predictable editing flows, fewer “where did the toolbar go?” moments.
- Smoother filtering with SelectAllSelector
- New dependency properties:
- FilterText: bindable filter value
- IsFilterActive: toggle filtering at runtime (great for simple/advanced modes)
- FilterWatermark: hint text for discoverability
- Result: Clean MVVM bindings, easier A/B tests for filter UX, happier users.
Developer tips
- Centralize theme tokens (radius, font weights, colors) in a ResourceDictionary and bind via AppearanceProperties.
- Register the new converters in App.xaml or a shared theme dictionary to reuse across views.
- For the RichTextBoxFormatBar, reserve space or host it in a dedicated toolbar region when using AlwaysVisible.
- Debounce FilterText changes in the ViewModel for very large collections to keep typing responsive.
Who benefits most
- WPF teams mixing Xceed Toolkit Plus for WPF and Xceed DataGrid in one solution
- Apps standardizing on rounded, modern UI without rewriting templates
- Products with rich text editing and discoverable filtering experiences
Commencez votre free 45‑day trial to test conflict‑free Toolkit + DataGrid in your app: https://xceed.com/trial/
Need help with migration or styling patterns? Our engineers are here to help: https://xceed.com/support/
FAQ
What’s the key change in Xceed Toolkit Plus for WPF 5.1?
The DataGrid assembly was renamed to Xceed.Wpf.DataGrid.Toolkit.dll, enabling conflict‑free mixing of Toolkit and the full DataGrid in the same application. This reduces version friction in modular solutions.
Will this break my XAML?
If you reference assembly-qualified XAML namespaces, update them to match the new assembly. Standard CLR namespace mappings typically keep working once references are updated.
How do AppearanceProperties reduce XAML boilerplate?
AppearanceProperties exposes radius, margin, foreground, and font weight for controls that didn’t previously surface them. You avoid template forks and keep styles centralized and consistent.
Where should I use the new converters?
Use CornerRadiusToUnderlineMarginConverter to align underlines with rounded edges, and CornerRadiusReplacementConverter to standardize radii in nested elements—cards, popups, lists, and menus.
How do I keep the RichTextBoxFormatBar from overlapping content?
Anchor it via Position/FormatBarPosition and place it in a dedicated toolbar region or reserved layout space for predictable UX.
What’s the best way to implement filtering on large lists?
Bind FilterText and IsFilterActive, show a helpful FilterWatermark, and add a short debounce in your ViewModel to maintain snappy input on big collections.