Hi Tobias,

The initializers of DatePicker without a parameter or with DatePickerModel parameter can not use default framework of Mvc related to persistance. The client value actually comes to server as HttpContext.Request.Form[id] or similar, but Mvc framework is not able to make use of that. If application needs to get value from client, then it should use Mvc standard initializers like DatePickerFor(expression) or DatePicker(string).

For example, if application model has fields like

public class MyModel
{
 public DateTime Date1 { get; set; }
 public DateTime Date2 { get; set; }
 public string DateString { get; set; }
}

and its view creates editors like

<%: Html.Infragistics().DatePickerFor(m => m.Date1).Render() %>
<%: Html.Infragistics().DatePicker("Date2").Render() %>
<%: Html.Infragistics().DatePicker("DateString").Render() %>
<%: Html.Infragistics().DatePicker().ID("DateString2").Render() %>

then within a controller, an application may get client values as following

[HttpPost]
public ActionResult MyAppAction(MyModel model, string returnUrl)
{
  DateTime date1 = model.Date1;
 DateTime date2 = model.Date2;
 string dateString = model.DateString;
 string dateString2 = HttpContext.Request.Form["DateString2"];
 ...
}

Note: if string-field is used by application model for DatePicker, then client value will come as 7 date fields in format: yyyy-M-d h:m:s.f. For example: 2012-8-21 0:0:0.0. It means that application should do some efforts to extract date fields and make sense of them. So, it is prefferable to use model-field with type of DateTime.