Most of the .NET developers would be well aware of what is Telerik RAD(Rapid application Development) controls. Telerik RAD controls are for those developers/organization which want to build Rapid applications with minimal effort. If you spend 6 weeks on developing a control that implements certain features necessary for business, which still need to go through certain quality guidelines and you may expect certain breakages which make your development time to say 10 weeks. Consider if there is already something similar available on the market, proven it’s capabilities and went through certain quality process. Business should think of reusing that component and cut down that 10 weeks works to say 1 or 2 weeks for implementing that control. This makes developers to ensure increased productivity and rapid application development.

Telerik is one of such company produces innovative reusable components for various .NET Applications. It is available for Windows Phone Applications, Web Applications, Silverlight Applications, Windows Applications and WPF Applications, you name it Telerik will make it for you.. I have worked with Telerik RAD AJAX, Phone 7, ASP.NET Controls, Silverlight and ASP.NET MVC(for MVC basic set of controls been released as open source). It is really nice and easy to implement there controls, because of the widely available documentation, samples and Telerik Community Support.

Recently Telerik has introduced a new member to their WPF and Silverlight controls familly, Telerik RadDataServiceDataSource. RadDataServiceDataSource provides seamless integration between an user interface and data coming from a WCF Data Service. The WCF Data Services technology enables the creation and consumption of OData services for the web. If you want to learn more about the relationship between the two, you may read the whitepaper WCF Data Services and OData At-a-Glance.

I will just quickly walk you through official blog by Rossen Hristov

Quoting from Rossen Hristov‘s blog

With this new control, you can retrieve, shape and edit data using declarative XAML syntax only. RadDataServiceDataSource provides extensive code-behind API for more advanced scenarios. The QueryableDataServiceCollectionView<T> class, which is internally used by the control, is made publicly available for use in view models part of an MVVM architecture, where the usage of UI elements is not recommended.IC392644

RadDataServiceDataSource for WPF was built on top of the WCF Data Services Client Library. RadDataServiceDataSource for Silverlight was built on top of the Silverlight version of the client library respectively. The WPF and Silverlight versions of the control have APIs that are 100% identical.

RadDataServiceDataSource uses a DataServiceContext and a DataServiceQuery<T> to communicate with the server. Thanks to the fact that all controls are part of the Telerik family, RadDataServiceDataSource can codelessly integrate withRadGridView, RadDataPagerand RadDataFilter and perform paging, filtering and sorting directly on the server. RadDataServiceDataSource can also be used as a standalone data source control since it provides the public API needed for loading, shaping and editing data.


  • Codeless integration with RadGridView, RadDataPager and RadDataFilter. Since all of the controls share the same data engine logic, when data-bound together they are able to detect each other automatically and start exchanging information. Linking RadGridView, RadDataPager and RadDataFilter to a RadDataServiceDataSource is as easy as binding them to its DataView property. All operations such as paging, filtering and sorting will automatically happen on the server without a single line of code.
  • Filtering can easily be performed through the FilterDescriptors collection of the control. This can either be done manually by the developer through editing the collection in code-behind or it can be left to controls such as RadGridView or RadDataFilter which will automatically translate their filtering criteria and apply it to RadDataServiceDataSource without a single line of code.
  • Sorting can easily be performed through the SortDescriptors collection of the control. This can either be done manually by the developer through editing the collection in code-behind or it can be left to RadGridView which will automatically translate its sorting criteria and apply it to RadDataServiceDataSource without a single line of code.
  • Paging can easily be performed through the paging API that the control provides. It can be done manually by the developer through methods from the MoveTo*Page family and properties such as PageIndex and PageSize. Or it can be left entirely to RadDataPager which will automatically page on the server when bound to RadDataServiceDataSource.
  • Editing is as simple as adding, removing or editing entities in the DataView of the control and then calling the SubmitChanges/RejectChanges methods. These operations can also be left to RadGridView which will automatically transfer them to the RadDataServiceDataSource.
  • MVVM support is provided by the public QueryableDataServiceCollectionView<T> class, which is the view that RadDataServiceDataSource internally uses. The RadDataServiceDataSource control is simply a thin-wrapper over this collection view, which performs all of the heavy lifting. This allows you to use it inside your view models without losing any functionality that the control would otherwise provide.

This is going to be interesting right. A single control can server all our purpose for connecting to different data sources. Telerik always does like that, superior in thinking through what any developer will need?. Thanks Telerik!!!

You need Code Samples and more information. Follow the link below.

Reference Link :