chinboy
2.9 KiB
AtomUI 6.2.5 API Change Examples
AtomUI 6.2.5 fixes Window fallback backgrounds on runtime theme changes. The package version also changes the identities of public generated registration group types. Rebuild compiled consumers when upgrading.
Chinese version: AtomUI 6.2.5 API 变更示例.
Quick reference
| Area | 6.2.4 | 6.2.5 migration |
|---|---|---|
| Generated registration groups | Public AtomUI.Generated.*.ControlPackageGroup_* types contain the 6.2.4 assembly identity in their generated names |
The versioned assembly identity produces different type names. Upgrade related packages together, rebuild compiled consumers and custom control packages, and republish trimmed/NativeAOT applications. Do not refer to the generated names directly. |
| Window fallback background | The opaque content surface can retain the old theme background after a runtime theme change | No API action. The surface now follows the effective TransparencyBackgroundFallback while Avalonia continues to control transparency transitions. |
1. Rebuild generated registration consumers
The public ControlPackageGroup_* type names change in AtomUI.Controls, AtomUI.Desktop.Controls, AtomUI.Toolkits.GalleryBase, AtomUI.Desktop.Controls.DataGrid, AtomUI.Desktop.Controls.ColorPicker and AtomUI.Desktop.Controls.Extras. The generator hashes the package assembly identity, which includes the package version, into each group name. A precompiled consumer that references a 6.2.4 group type cannot bind to the corresponding 6.2.5 type.
Upgrade all related AtomUI packages and the Generator together. Rebuild applications and custom control packages that consume generated registration metadata, then republish trimmed or NativeAOT applications so linking uses the current groups. Ordinary UseAtomUI() and package registration calls remain the supported entry points. Replace any direct reference to AtomUI.Generated.*.ControlPackageGroup_* with those APIs; generated group names have no stable alias.
This is a generated public-identity change, not a change to the TypeMap registration mechanism. Package API validation against 6.2.4 reports one CP0001 per affected package and target framework: 12 diagnostics across the six packages, with no other API differences in the 20-package comparison. These diagnostics are intentional incompatibilities and must not be suppressed or described as a passing binary-compatibility check. Package layout is validated separately.
2. Verify Window theme changes
The Window content surface now updates its opaque fallback background when the effective TransparencyBackgroundFallback changes, including runtime theme changes. Explicit local fallback values continue to take precedence; transparent surfaces keep Avalonia's existing behavior. No API or theme-key migration is required. Verify theme switching in applications with custom Window templates or explicit fallback backgrounds.