I have been chasing a bug this morning where a date was not properly saved.
I turned out that when initialising the ASPxDateEdit Value property to a SmartDate it converts the date into a 'US actual date' (i.e. swaps day and month) I use British regional settings (dd/M/yyyy).
SmartDate value is 6 March 2012
when setting the ASPxDateEdit Value property the ASPxDateEdit date actually becomes 3 June 2012 !
when setting the ASPxDateEdit Date property it works correctly.
As a test I converted the SmarteDate properties in my business object to DateTime? types and then the ASPxDateEdit worked fine. (both Value and Date properties)
DateTime? should be fine for our needs, but would prefer to use SmartDate. Are there any issues in using DateTime?
DefaultFormat for SmartDate is "d" .
Do you use remote dataportal?
This code in LinqPad (http://www.linqpad.net):
var sd = new SmartDate(DateTime.Now);
gives this output:
Copyright (c) Marimer LLC