.NET RIA Services Overview
page 3 of 4
by Sergey Zwezdin
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 21522/ 32

Data sources

Working under the application programming we saw, that ADO.NET Entity Framework was a data source. We also saw that, at platform level, the class containing business operations was allocated. Such allocation in a separate class allows us to abstract certain client technologies and data sources. So, data sources can be datastores based on POCO, services and datastores with custom logic. Similar reasoning is fair for a client part. The .NET appendix (Silverlight, WPF, etc), JavaScript code, services, etc. can be a client for such service. In fact, building business logic once means it can be used repeatedly.

Figure 5: Overview of concept of .NET RIA Services

Besides that, allocation of a central object with business logic that does not depend on representation and data source makes it possible to build unit tests for it and to develop such applications in Test-Driven-Development style.

View Entire Article

User Comments

Title: Lead Developer   
Name: Don B
Date: 2009-11-06 7:50:37 AM
Perhaps George shouldn't start drinking before Noon. I wonder how many languages he can intelligently converse in or if he is capable of adding anything meaningful to the actual topic.
Title: Lead Programmer   
Name: George Wilson
Date: 2009-11-02 11:56:02 AM
This article is poorly written. It reads as if Yoda wrote it, "Problem resovled in new platform it is...mmmm...yes!"

Product Spotlight
Product Spotlight 

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024 ASPAlliance.com  |  Page Processed at 2024-02-26 7:45:27 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search