Below are some code snippets that can help you achieve the desired result. The code uses a member variable for storing items' contents:

private MemoryStream save = null; 

Here is the code that saves the currently selected items in a memory stream:

if (save != null)
{
      save.Dispose();
      save = null;
}

// Create the buffer
save = new MemoryStream();

// Create the buffer writer
BinaryWriter writer = new BinaryWriter(save);

// Create the serialization context
BinarySerializationContext context =
      new BinarySerializationContext(calendar1.Schedule);

// Save the item count
writer.Write(calendar1.ItemSelection.Items.Length);

// Save the selected items
foreach (Item item in calendar1.ItemSelection.Items)
{
      // Save the item Id. This will help us detect whether the
      // item already exists in the schedule before loading
      writer.Write(item.Id);

      // Save the item itself
      item.SaveTo(writer, context);
} 

Here is the code that loads the previously saved appointments.

if (save == null)
      return;

// Seek to the beginning of the stream
save.Seek(0, SeekOrigin.Begin);

// Create a buffer reader
BinaryReader reader = new BinaryReader(save);

// Read the item count
int count = reader.ReadInt32();
if (count == 0)
      return;

// Create the deserialization context
BinarySerializationContext context =
      new BinarySerializationContext(calendar1.Schedule);

// Read the items
for (int i = 0; i < count; i++)
{
      // Read the id
      string id = reader.ReadString();

      // Check if an item with this id already exists
      Item item = calendar1.Schedule.Items[id];

      // If the item doesn't exist, create it.
      // Note: in the general case we have to be aware of the actual
      // type of the item that was serialized. For the purposes of
      // this sample we will assume its type is an Appointment
      if (item == null)
      {
            item = new Appointment();
            calendar1.Schedule.Items.Add(item);
      }

      // Load the item's contents from the stream
      item.LoadFrom(reader, context);
} 

Meppy

When applying the changes on the target machine, you need to apply them to the occurrence that has been changed, rather than the master item of the recurrence. Applying the changes to the master item (the one you assign the Recurrence object to) will cause them to affect all items in the recurrence sequence. In order to retrieve an individual occurrence of a recurrence pattern, invoke the GetOccurrence method of the Recurrence object and supply the index of the occurrence of interest. The method returns an instance of the Item class representing the occurrence with the specified index. For example, if you change the 5th occurrence of a recurring sequence and you want to transfer the changes to the target machine, remember the occurrence index (5), then when applying the changes to the target machine, invoke the GetOccurrence method and supply 5 as its first argument. Then, apply the changes to the returned Item instance.

Let me know if this is clear enough.

Meppy

Figured I'd jump on this topic instead of creating a new one since my question is also related to serialization of appointments.

I have my own C# class that inherits from the MindFusion.Scheduling.Appointment class (call it AppointmentClass). I have created my own XML serialization to serialize some of the existing Appointment properties, like ID, Subject, etc, as well as some properties I've added. I am also serializing/deserializing the Contacts collection from the Appointment (similar to the Appointment, I have a new ContactClass that adds several properties to the Mindfusion.Scheduling.Contact class, and is serialized in the same manner).

My problem is, after deserializing the AppointmentClass objects and adding them to the schedule, they do not actually display on the schedule once the schedule is closed. That is, when I check the Schedule.Items collection in the debugger after deserialization, they are present, with the correct properties/IDs of the original Appointments prior to serialization. Is there perhaps some property on the Appointment class that isn't being set after I deserialize, and is causing this? Thanks.

Thanks for the quick response Meppy.

I am using grouping, and I already have the grouping set (GroupByContacts). My Calendar.Contacts collection already contains the list of ContactClass objects, some of which will be in the AppointmentClass.Contacts list.

Nothing has changed with either of these two properties.

Is it correct that the only field required to match up on the Contacts in these two groups (Appointment.Contacts and Calendar.Contacts) for the appointment to show up under the contact on the calendar is the Contact.ID? Thanks.

That did the trick, I was taking that for granted before when not serializing that I was using the exact same Contacts. Thanks for the help Meppy, keep up the good work.