Content deleted Content added
mNo edit summary |
Disambiguated: WPF → Windows Presentation Foundation, WCF → Windows Communication Foundation (2); formatting: whitespace (using Advisor.js) |
||
Line 21:
===Metastate maintenance===
CSLA .NET manages the ''metastate'' about each business object. For example, each business object tracks information about when it is new (it represents data that hasn't been saved yet) and when it is dirty (it needs to be saved to the database either because it is new or because its member data has been changed since it was last loaded). Business objects can also be marked for deletion so they can later be deleted (for example when a user has pressed a button confirming his or her intention to delete the rows.)
===''n''-Level undo===
Line 33:
==''Extended features of CSLA''==
===Simple UI creation===
Business objects created using CSLA .NET fully support data binding for all [[Microsoft .NET]] UI technologies, including [[Windows Runtime]] ([[WinRT]]), [[Windows Presentation Foundation|WPF]], [[Web Forms]], [[ASP.NET MVC]], [[Windows Phone]], [[Silverlight]], and [[Windows Forms]]. Data-bound controls like DataGrids and ListBoxes can be bound to business objects instead of more generalized database objects like [[ADO.NET]] DataSets and DataTables.
===Distributed data access===
The CSLA .NET framework implements a concept called [[mobile objects]] or [[mobile agents]] to allow objects to move across network boundaries using [[Windows Communication Foundation|WCF]], [[Web Services]], or other technologies. As a result the data access enjoys [[___location transparency]], meaning that the logic may run on the client workstation or server depending on the application's configuration. It can also be configured to use manual [[database transaction]]s or distributed [[two-phase commit]] transactions.
Data access logic is cleanly separated from business logic, and can be implemented using any data access technology available on the [[Microsoft .NET]] platform. Examples include [[ADO.NET Entity Framework]], raw [[ADO.NET]], [[nHibernate]], etc.
===Web Services support===
Business logic created with the CSLA .NET framework can easily be exposed as a web service to remote consumers. This can be done using server-side [[Microsoft .NET]] technologies such as [[Web API]], [[Windows Communication Foundation|WCF]], and [[asmx web services]].
==References==
| |||