Apologies if this has been addressed in another thread... I searched but couldn't find anything relevant or a link back from the issue itself.
I see this issue (see link below) relates to CSLA 4 and my question is whether this should apply to CSLA 3.8 also or is this unique to CSLA 4?
Issue 794 - http://www.lhotka.net/cslabugs/edit_bug.aspx?id=794
That enhancement was made to CSLA 4.
Copyright (c) Marimer LLC