This document is the change log for version 2.1.1 of CSLA .NET.
Known issues:
|
CslaDataSource |
It does not work to add a CslaDataSource to a page by choosing to “add a new data source” from within the GridView or DetailsView controls. Attempting to do this will result in an exception that prevents the control from displaying properly. I have been unable to resolve this issue, but there is a viable workaround.
You must manually add a CslaDataSource control to your page, either using drag-and-drop from the Toolbox, or by typing the tag into the page. Then you can configure the assembly/type information in the data source control. Then you can choose this data source control as the data source for your GridView or DetailsView control. |
Changes and Enhancements:
Csla – ValidationRules
Fix a bug that prevented dependant properties from working correctly in the case that both per-type and per-instance validation rules are used in an object. The dependency list is now merged into the current rules-to-check, along with the validation rules themselves.
Csla – ValidationRules
Include the name of the rule method when raising the invalid operation exception that occurs when you try to call AddRule() to add an instance method of the business object as a per-type rule. Including the method name assists with debugging in this case.
Csla – Web\CslaDataSource
In the SelectObject event implementation, a page could return null/Nothing for e.BusinessObject. In that case, the CslaDataSource control now returns an empty list to data binding, rather than a list containing that null value. This makes data binding properly handle the case of an empty object as a result.
Csla – FilteredBindingList
Return the adjusted index value from the Find() method, rather than the index value from the underlying list.
Csla – SortedBindingList
Return the adjusted index value from the Find() method, rather than the index value from the underlying list.