Recently MVC 3 was released which is a good reason for me to update our RESTful web service framework. This latest version is compiled against ASP.Net MVC 3 and .Net 4. I have also taken the opportunity to introduce some new features that have either been requested or come out of actual implementations.

More...

When ASP.Net MVC 2 came out, it included support for overloading POST requests, something I had previously incorporated into our RESTful framework. The release also came with the latest incarnation of Microsoft’s experimentation with providing a RESTful framework for ASP.Net MVC (this is part of the ASP.NET MVC 2 Futures download). I looked at their first offering in an earlier post when it was known as the “Rest for ASP.Net MVC SDK”. It had some interesting ideas, but wasn’t comprehensive enough for me. So with this new release, I was keen to see if I could retire our framework (or at least parts of it) and use some of the new features. So here I’ll look at each feature I’d like to see in a RESTful web service and see how well it is supported, as well as look at some new ideas altogether.

More...

Now that ASP.Net MVC 2.0 is out, I’ve upgraded the RESTful Web Service to use it. I’ve also taken this opportunity to round up the features we have built into the RESTful web service support so far.

More...

In this series of posts, I have concentrated upon creating a truly RESTful web service… it has not been a priority to use the full power of ASP.Net MVC’s extensibility. However, this has resulted in a solution that is too intrusive into ASP.Net MVC. The consequences being, any web service developed with the Shoulders of Giants DLL can be difficult to write unit tests for or extend in other directions… so with this and my previous post, I hope to address this.

More...

A little while back I reviewed the Rest for ASP.NET MVC SDK that was released by Microsoft WCF team. I liked some of the ideas it contained so promised to bring some of those into our code. Well, I’ve finally started to do that.

More...

I have been doing most of my ASP.Net MVC RESTful web service development on IIS6 or IIS7. Recently however, I tried it on Windows 7 RTM using IIS7.5. Using the “Classic .Net AppPool” everything worked great. Then I tried the “DefaultAppPool” (i.e. using Integrated Mode). Everything seemed fine… until I wanted to PUT a new resource and DELETE a resource.

More...

Just a quick post after I’ve spent a merry afternoon trying to configure a Windows XP machine to allow a developer, who hasn’t got Local Administrator rights, to debug an ASP.Net application. This is a subject covered elsewhere including on the MSDN site.