At first, I want to give you an overall picture of all Scheduler versions (legacy, current and future).
Currently we ship Scheduler controls for the next platforms:
- WinForms (home page). C1.Win.C1Schedule.2.dll assembly includes C1Schedule and C1Calendar controls. It is built with .Net 2.0;
- ASP.Net (home page, live demo). There are 2 versions. C1.Web.C1Schedule.2.dll is a legacy version built with .Net 2.0. The C1Schedule for .Net 3.5 is a part of C1.Web.UI.Controls.dll assembly. It will replace legacy version in the nearest year;
- WPF (home page, live demo). C1.WPF.C1Schedule.dll assembly includes C1Scheduler, C1MonthCalendar, C1MultiMonthCalendar, C1DateTimePicker, C1TimeSpanPicker controls. It is built with .Net Framework 3.0;
- Silverlight 3 (home page, live demo). C1.Silverlight.Schedule.dll assembly contains C1Scheduler control. It uses controls from C1.Silverlight.dll, C1.Silverlight.Data.dll and C1.Silverlight.DateTimeEditors.dll assemblies.
All Schedulers share the same object model defined in C1.C1Schedule namespace. Actually, the most of that is represented by the shared code. So, if you know how to create Appointment from code in WinForms version, then you can be sure that you know how to do that in Silverlight version.
All Schedulers are data-compatible. If you saved xml data with WinForms Scheduler, you should be able to load this data with WPF or Silverlight versions. If you have database with C1Scheduler data, you can use it with any Scheduler version.
Roadmap for 2010 V1
- WinForms: new version built against .Net Framework 4.0 Client Profile (perhaps we’ll ship it after Microsoft releases VS 2010);
- Silverlight 4 version. It will be compatible with Silverlight 3 version;
WPF: 2010 V1 release will contain 2 assemblies compatible with Silverlight version: C1.WPF.DateTimeEditors.dll and C1.WPF.Schedule.dll.
You see, we tend to make our WPF and Silverlight studios compatible with each other. We share code between WPF and Silverlight versions and we want you to have this ability as well. In the future, these assemblies will go together with their Silverlight counterpart. 2010 V1 version is built against .Net Framework 3.5 Client Profile and has design-time support for VS 2008, VS 2010, Blend 2 and Blend 3.
For 2010 V2 release we are planning to add multi-month calendar control to Silverlight and new WPF versions. When it is ready, old WPF version will go into maintenance mode. Old WPF version will remain compatible with pure .Net 3.0. If your clients use Windows XP machines without .Net 3.5 installed, you can continue using this version.
We haven’t decided yet, what Framework version will be supported by the new WPF Scheduler. Perhaps, we’ll move to .Net 4 when it is released, or will ship both .Net 3.5 and .Net 4 versions. Feel free to leave your feedback; we have time to take it into account.
Next time I’m going to write about WPF and Silverlight versions in more details: distinctions, compatibility issues, etc… If you have questions – don’t hesitate to ask.