I am in the midst of putting together a blog / screencast series illustrating developing Silverlight 3 application, taking advantage of various design patterns. Some of the patterns we will cover are the Repository, the Pipeline, the Service Agent and Model View ViewModel. I will be building a Sample HelpDesk Application along the way (see below).[ Read More → ]
In yesterday’s post, I build our Repository interface and the implementation, as well as added some server-side validation, following a simple pattern. I also added a test project and wrote some tests to test the our validation logic. In this post I will implement the Pipeline pattern. I will then implement a fake repository and use it to test our Pipeline.[ Read More → ]
In this post I will provide a brief overview of the Repository pattern, implement a Repository in our sample application, establish our server-side validation and add our test project.
Most of what you will see in this post follows very closely with the code ScottGu implemented in his NerdDinner tutorial. In fact, I would highly [...]
During the summer I put together a session on Patterns-Based Silverlight Development that we delivered across the West Region as part of MSDN events. The session was structured around building a Silverlight application from the ground up that illustrated the use of the following design patterns: 1) Repository, 2) Pipeline, 3) Service Agent and 4) [...]
This is part 3 in this series where I am building an Azure shopping cart application from the ground up. In this post, I will create a RESTful service using WCF and host it in Windows Azure. This service will source it’s data from Azure Table Storage. I will then illustrate how to consume this service from a Silverlight component hosted in Windows Azure. Giddyup.
(In part 2 I illustrated how to set up and access Azure Table Storage in both the development environment, as well as in the cloud. I created a Wine table, added a few entities and retrieved them both locally and from the cloud. I did all this taking advantage of the ADO.NET Data Services .NET Client Library and the StorageClient sample application.)[ Read More → ]
A common scenario you may encounter when designing your RESTful services is supporting clients that only work with GET and POST. Two such clients on our stack are Silverlight 2 and our ASP.NET AJAX Client Libraries (out of the box). This brings about a quandary: should I design a HI-REST service interface (support GET, PUT, POST, DELETE) and not support these clients or should I design a LO-REST service interface (only support GET and POST) and support clients such as these. Fortunately, for you, these are not the only answers to this problem.
In this post, I will illustrate how to "tunnel" PUT, DELETE or any other HTTP Method over POST. What I mean by tunneling over POST is that you actually use an HTTP POST, but you pass additional information that allows your call to be routed to the appropriate service operation that supports other Methods. In this case, we will support passing the "real" method we want to call in an X-HTTP-Method-Override HTTP Header. This would have been a chore prior to the release of the WCF REST Starter Kit. Now, however, it is quite simple. Let’s take a look…[ Read More → ]
As some of you know, I am in the midst of a blog series on REST in WCF. Further, I have been hard at work on a series of screencasts on the same subject (in conjunction with Ron Jacobs). My colleague Tim Heuer relayed to me that I didn’t have a single post that we can point a person to that provides links to all of the posts and screencasts. I will keep this post updated with all of the info:
Blog Series:[ Read More → ]