I have completed the MVVM restructure of the ClassicCalendar, ClassicCalendarExt, DatePicker, and DayPicker. This is a full MVVM model and there is no code behind in the control classes only in the viewmodel. I have added commanding and event routing to accomplish this fully structured model. I have also updated the demo app to include xaml and code examples of how to create each of these three controls. I also removed the xml file for loading the selected dates in the display mode of the ClassicCalendar and ClassicCalendarExt. The dateranges and dayvalueselections are now passed in through the viewmodel via the datacontext on the page loading the control. This way the user can load any date ranges they choose and pick the way they wish to load them (i.e. Database, xml, other file formats). I will add a xml file loader to the next release as an example of a way to load the date ranges by xml.Application Notes:
- Silverlight 4.0
- Visual Studio 2010
- Silverlight Toolkit 4.0
- Includes Asp.Net host and Silverlight demo project to display the controls.