Felix @ Planet

Now that we’ve done all the hard work creating hooks and interfaces in previous posts creating the actual Selector is relatively simple.

In this post we are quickly going to discuss the need for a consistent way for our binding controls to let our selector class know exactly what to project. I will illustrate the problem by comparing the telerik controls RadComboBox and RadGrid.

In this part we will derive from ObjectDataSource to put in place a hook that our selector can latch onto. When delving into the workings of the ObjectDataSource it also became clear that we have to also override the ObjectDataSourceView that it uses. The location of the hook actually sits here.

When upgrading to use Entity Framework we are also in the process of trying to change all appropriate business layer calls to IQueryable – the main point of which was so that our UI can define specific projections on the data as it needs. Unfortunately we found no way that we could attach to a BL using some kind of DataSource and have this projection capability. So this post is out to create one.

In this post I’m going to talk about extending EF entities to encapsulate common functionality. For this particular case I will expand upon the concept in this blog post EF4 Part 2: EDM Inheritance Pains.

Phew it’s been a while but I better get back into it! In the final part of this series I will be going over what we can do client side when we want to query our services. Because of the nature of WCF Data Services to detach our client objects from our server ones this is more of a general discussion about its querying capabilities.

I am going to come back to Part 1 in this post and see how we can leverage the business repository classes and the T4 text generator to create automatic service points. This means we would never have to touch the service layer as it will automatically grow as we added repositories.

In this part of my WCF Data Services Custom Framework series I will implement the IUpdatable interface in our WCF Data Services container. I will do it in such a way to take advantage of the business entities and repositories created in Part 2.

In Part 1 we exposed a service which was a piece of cake! In this part we will lay the foundations for exposing Save/Update/Delete operations easily using Business Repositories.

In this series I’m going to construct a service using WCF Data Services (which exposes an OData feed) with Update/Insert/Delete functionality. There is a catch though, I want to avoid exposing database entities so I cant take advantage of WCF’s out-of-the-box implementation of the ADO .NET Entity Framework.