WPF Scheduler (SfScheduler) Implementation

When to Use This Skill

• Implement calendar or scheduler functionality in WPF applications
• Create appointment management systems
• Build resource scheduling applications
• Implement meeting or event management interfaces
• Add Outlook-like calendar views to applications
• Schedule and manage recurring appointments
• Handle multi-resource scheduling scenarios
• Display appointments across different timezones
• Implement drag-and-drop appointment rescheduling
• Create custom appointment editors or views

Component Overview

• 8 Built-in Views: Day, Week, WorkWeek, Month, TimelineDay, TimelineWeek, TimelineWorkWeek, TimelineMonth
• Appointment Management: Normal, all-day, spanned, and recurring appointments with full CRUD operations
• Resource Scheduling: Multi-resource support with grouping by resource or date
• Drag-and-Drop: Intuitive appointment rescheduling with visual feedback
• Recurrence Patterns: Daily, weekly, monthly, yearly with exception handling
• Timezone Support: Multiple timezone handling with automatic DST adjustments
• Built-in Editor: Appointment creation and editing with validation
• Customization: Extensive styling, templates, and appearance options
• Accessibility: WCAG compliance with full keyboard navigation
• Advanced Features: Load-on-demand, reminders, localization

Documentation and Navigation Guide

Getting Started

• Assembly deployment and NuGet packages
• Creating basic scheduler application (Designer, XAML, C#)
• Basic appointment setup and configuration
• First day of week and theme support
• Initial setup and quick start examples

Views and Display

• Available view types (Day, Week, Month, Timeline variants)
• ViewType property and switching between views
• View-specific features and rendering
• Current date display

• Time interval and slot height customization
• Working days and hours configuration
• Special time regions (lunch breaks, holidays)
• Selection restrictions in timeslots

Appointments and Data

• ScheduleAppointment class and properties
• Creating and managing appointments
• ItemSource and AppointmentMapping
• Custom business objects and data binding
• All-day and spanned appointments
• Recurrence appointments and patterns (RRULE)
• Recurrence exceptions

• Built-in appointment editor
• Creating, editing, and deleting appointments via UI
• Editor customization and validation
• Editor events and custom logic

• Drag-and-drop functionality
• Rescheduling appointments
• Drag-drop restrictions and events

Resource Management

• Resource concepts and SchedulerResource class
• ResourceGroupType (Resource vs Date grouping)
• Assigning resources to appointments
• Multi-resource scheduling
• Resource appearance customization

Calendar and Time Management

• Calendar systems (Gregorian, custom)
• Calendar configuration

• DisplayDate property
• Programmatic navigation methods
• Date change events

• Scheduler and appointment timezones
• Automatic timezone conversion
• Daylight saving time handling
• Multi-timezone scheduling scenarios

UI Customization

• Header customization and templates
• Context menu and commands
• Busy indicator
• Selection modes and events

Advanced Features

• Accessibility (WCAG, keyboard navigation)
• Localization and culture-specific formatting
• Load on demand for large datasets
• Reminders and notifications
• Migration from SfSchedule to SfScheduler

Quick Start Example

Basic Scheduler with Appointments

<Window xmlns:syncfusion="http://schemas.syncfusion.com/wpf">
    <syncfusion:SfScheduler x:Name="Schedule" 
                            ViewType="Week"
                            FirstDayOfWeek="Sunday" />
</Window>

using Syncfusion.UI.Xaml.Scheduler;

public MainWindow()
{
    InitializeComponent();
    
    // Create appointment collection
    var appointments = new ScheduleAppointmentCollection();
    
    // Add sample appointment
    appointments.Add(new ScheduleAppointment
    {
        StartTime = DateTime.Now.Date.AddHours(10),
        EndTime = DateTime.Now.Date.AddHours(12),
        Subject = "Client Meeting",
        Location = "Conference Room A",
        Notes = "Discuss project timeline",
        AppointmentBackground = Brushes.LightBlue
    });
    
    Schedule.ItemsSource = appointments;
}

Common Patterns

Pattern 1: Custom Appointments with Data Binding

// Custom business object
public class Meeting : INotifyPropertyChanged
{
    public string EventName { get; set; }
    public DateTime From { get; set; }
    public DateTime To { get; set; }
    public Brush Color { get; set; }
    public bool IsAllDay { get; set; }
}

// ViewModel
public class SchedulerViewModel
{
    public ObservableCollection<Meeting> Events { get; set; }
    
    public SchedulerViewModel()
    {
        Events = new ObservableCollection<Meeting>
        {
            new Meeting
            {
                EventName = "Team Standup",
                From = DateTime.Now.Date.AddHours(9),
                To = DateTime.Now.Date.AddHours(9.5),
                Color = Brushes.Green,
                IsAllDay = false
            }
        };
    }
}

<syncfusion:SfScheduler x:Name="Schedule" 
                        ViewType="Week"
                        ItemsSource="{Binding Events}">
    <syncfusion:SfScheduler.AppointmentMapping>
        <syncfusion:AppointmentMapping
            Subject="EventName"
            StartTime="From"
            EndTime="To"
            AppointmentBackground="Color"
            IsAllDay="IsAllDay" />
    </syncfusion:SfScheduler.AppointmentMapping>
</syncfusion:SfScheduler>

Pattern 2: Recurring Weekly Meeting

var recurringMeeting = new ScheduleAppointment
{
    StartTime = new DateTime(2026, 3, 24, 14, 0, 0), // Monday 2PM
    EndTime = new DateTime(2026, 3, 24, 15, 0, 0),
    Subject = "Weekly Status Meeting",
    // Recur every Monday for 12 weeks
    RecurrenceRule = "FREQ=WEEKLY;BYDAY=MO;COUNT=12",
    AppointmentBackground = Brushes.Orange
};

Pattern 3: Resource-Based Scheduling

// Add resources
Schedule.ResourceCollection = new ObservableCollection<SchedulerResource>
{
    new SchedulerResource { Id = "1001", Name = "Dr. Smith", Background = Brushes.Blue },
    new SchedulerResource { Id = "1002", Name = "Dr. Jones", Background = Brushes.Green }
};

Schedule.ResourceGroupType = ResourceGroupType.Resource;

// Assign appointment to resource
var appointment = new ScheduleAppointment
{
    StartTime = DateTime.Now.AddHours(2),
    EndTime = DateTime.Now.AddHours(3),
    Subject = "Patient Consultation",
    ResourceIdCollection = new ObservableCollection<object> { "1001" }
};

Pattern 4: Timezone-Aware Appointments

var globalMeeting = new ScheduleAppointment
{
    StartTime = new DateTime(2026, 3, 25, 10, 0, 0),
    EndTime = new DateTime(2026, 3, 25, 11, 0, 0),
    Subject = "Global Team Sync",
    StartTimeZone = "Pacific Standard Time",
    EndTimeZone = "Pacific Standard Time"
};

// Scheduler displays in local timezone automatically
Schedule.TimeZone = TimeZoneInfo.Local.Id;

Key Properties Overview

Core Properties

View Navigation & Configuration

Date Range Properties

Data Binding & Mapping

Header Customization

Resource Scheduling

View-Specific Settings

Calendar & Culture

UI & Interaction

Context Menus

Drag & Drop

Appointment Editing

Load On Demand

Key Methods

Key Events

Common Use Cases

1. Meeting Room Scheduler - Manage conference room bookings with resource grouping
2. Medical Appointments - Doctor scheduling with patient appointments and recurring slots
3. Project Timeline - Track tasks, milestones, and team member assignments
4. Event Calendar - Public event management with all-day and multi-day events
5. Employee Shift Planning - Resource-based shift scheduling with drag-drop
6. Class Schedule - Educational timetables with recurring sessions
7. Service Booking - Appointment booking system with availability management

Important Considerations

• Performance: Use LoadOnDemand for large datasets spanning multiple years
• Data Binding: Custom objects must implement INotifyPropertyChanged for updates
• Recurrence: Use RRULE format for recurrence patterns (standard RFC 5545)
• Timezones: Always specify timezones for global applications
• Resources: ResourceIdCollection must match ResourceCollection IDs
• Views: Choose appropriate view based on use case (Day for detailed, Month for overview)

Next Steps