Component-based Scalable Logical Architecture: Difference between revisions

Revision as of 02:30, 23 February 2013

Revision as of 02:34, 23 February 2013

Line 45:

==''Extended features of CSLA''==

===Simple UI creation===

UsingBusiness objects created using CSLA .NET fully support data binding for all [[Microsoft .NET]] UI technologies, including [[Windows FormsRuntime]] or([[WinRT]]), [[WPF]], [[Web Forms]], data[[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 [[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 servicesservice to remote consumers. This can be done using server-side [[Microsoft .NET]] technologies such as [[Web API]], [[WCF]], and [[asmx web services]].

.

==References==