Building RESTful application using SQL Azure, WCF, ADO.NET Data Service & Telerik OpenAccess WCF Wizard
- Telerik OpenAccess WCF Wizard: How-to Video #1
- Telerik OpenAccess WCF Wizard: How-to Video #2- Astoria
- Telerik OpenAccess WCF Wizard: How-to Video #3- REST Collections
- Telerik OpenAccess WCF Wizard: How-to Video #4- ATOMPub
- Using WCF for Silverlight Development with Telerik OpenAccess
- Using ADO.NET Data Services with Telerik OpenAccess’s WCF Wizard
- Using The WCF REST Starter Kit and REST Collections with Telerik OpenAccess’s WCF Wizard
- Using The WCF REST Starter Kit and ATOMPub with Telerik OpenAccess’s WCF Wizard
- Building a RESTful application with SQL Azure
Hybrid choice that blends ASP.NET and WCF. The WCF team saw that many developers building ASP.NET MVC apps are more comfortable with the ASP.NET MVC programming model, but still want to supply more rich RESTful services from their web applications. So the WCF team put together an SDK and samples for building REST services using ASP.NET MVC.
You can download the samples and SDK from ASP.NET MVC 1.0 page on CodePlex.
Do read through the overview document as it describes the changes you’ll need to make to an application to make use of this framework. Also, the zip file includes several sample movie applications which demonstrate various scenarios and compares them to the baseline of not using the REST approach.
A common question that comes up is when to use ASP.NET MVC to build out REST-ful services and when to use WCF?
when the only reason for the service’s existence is to service the one application you’re currently building, it may make more sense would stick with the simple case of using ASP.NET MVC. This is commonly the case when the only client to your JSON service is your web application’s Ajax code.
When your service is intended to serve multiple clients (not just your one application) or hit large scale usage, then moving to a real services layer such as WCF may be more appropriate.
There are several reasons to consider using XHTML as the default representation for your ASP.NET MVC RESTful services. First, you can leverage the syntax and semantics for important elements like <a>, <form>, and <input> instead of inventing your own. Second, you’ll end up with services that feel a lot like sites because they’ll be browsable by both users and applications. The XHTML is still interpreted by a human—it’s just a programmer during development instead of a user at runtime. This simplifies things throughout the development process and makes it easier for consumers to learn how your service works. And finally, you can leverage standard Web development frameworks to build your RESTful services.
ASP.NET MVC is one such framework that provides an inherently RESTful model for building XHTML-based services. This article walks through some XHTML design concepts and then shows you how to build a complete XHTML-based RESTful service.
XHTML: Representing Data and Links
XHTML: Representing Input with Forms
Understanding the ASP.NET MVC Architecture
Implementing the Model
Implementing the Controller
Designing URIs with Routes
Implementing the Views
Consuming the Bookmark Service