What problem does it solve? Adding an Outlook-style calendar to a WPF application requires wiring up appointment data binding, field mappings, view configuration, recurrence, and appearance customization — a surface area large enough to cause common pitfalls like missing mappings, broken recurrence, and unresolved XAML namespaces. ## Core Features & Use Cases - Data Binding & Mappings: Bind appointments, resources, labels, statuses, and time regions via DataSource with AppointmentMappings, ResourceMappings, custom fields, and mapping converters. - Seven View Types: Configure Day, Work Week, Week, Month, Timeline, Agenda, and List views, switch at runtime with ActiveViewIndex, and group by resource or date. - Appearance Customization: Override AppointmentContentTemplate, apply per-view AppointmentStyle, and control colors with BrushSet and BrushProvider. - Use Case: Build a doctor's office scheduling app where appointments bind to a ViewModel, group into one lane per doctor, support recurring visits, and persist changes through AppointmentAdded/Edited/Removed events. ## Quick Start Add the DevExpress.Wpf.Scheduling NuGet package to a net8.0-windows WPF project and ask the AI to create a SchedulerControl bound to appointment and resource collections with the required Start and End mappings.
