This thread is related to another thread titled, "database table structure." Sorry for the overlap, but we're struggling to understand the recommended approach for persisting RadScheduleView Appointments to the database via WCF RIA Services. Questions:
- Do you have a more refined reference implementation solution similar to ScheduleView_EF_SL.zip?
- What is the proper structure for persisting Appointment recurrences and recurrence exceptions?
- Are you sticking with a virtually duplicated SqlAppointment entity (SqlExceptionAppointment) as the means to store recurrence exceptions?
The MVVM-related improvements to the RadScheduleView relative to the RadScheduler are excellent--thank you. However the ScheduleView_EF_SL sample is a bit confusing because of the switch away from implementing exceptions storage as self-referencing SqlAppointments. In addition, there appear to be columns left over from the self-referencing example (SqlAppointments.ParentId for example) that do not appear to be used in the sample.
Because we have a large solution, changing our database schema, Entity Framework data model, WCF RIA Service meta-data classes, and RIA [query], [update], etc., classes is a time-consuming operation. I want to be sure I head down the recommended path sooner rather than later.