Not having touched CSLA.NET framework for couple of months, I am requested to write a simple tutorial for developers at our China office. Great Rocky released CSKA.NET 2.1.3 two weeks ago. Several new features have been added. So I decided to read the book again and write some important notes here. Hope this could also improve my DotNet knowledge and OO Thinking.

Here are some useful points I picked from the book:

• To enable the objects for Data Binding, the business objects must implement following three interfaces: IEditableObject, INotifyPropertyChanged, IBindingList
• Generic types are not polymorphic like normal types. That's the primary reason for pulling the functionality out of the generic class into a normal class in CSLA.Net. ( BusinessBase<T> inherits from Csla.Core.BusinessBase)
• The goal in object design is to ensure that a given behavior exists only once with the object model while the relational modeling requires that a given data element should exist exactly once in the data model.

You have to combine these two faqs together to make it work:

http://faq.1and1.com/scripting_languages_supported/asp_net/dotnetnuke/4.html

http://faq.1and1.com/scripting_languages_supported/asp_net/dotnetnuke/3.html

Note: For visitors of your site, this entry is only displayed for users with the preselected language English/English (en)

CSLA.Net 2.1 has been released. It comes with several new features. Some useful ones I am going to use in Smart Bridge SA is :

• Per-type validation rules.
• Per-type authorization rules.
• Severity Classification.