Another Cross Domain iFrame Communication Technique

August 17, 2009 23:34 by admin

Recently I created a web page that hosted an iFrame. The contents of the iFrame were served from another domain. That content would use JavaScript to hide and show some HTML elements. As the iFrame’s content changed, I didn’t want scroll bars to appear or some of the content to be hidden (if I applied scrolling="no"). I could have just made sure the iFrame was big enough to contain the maximum content... but I wanted a more dynamic solution that made the iFrame appear more integrated with its parent page. I needed the parent page to adjust the size of the iFrame as the content size changed.


Comparing Word Documents in Team Foundation Server

May 19, 2009 23:28 by admin

We’re thinking about putting some of our Microsoft Word documents under source control in our Team Foundation Server. It would be great to be able to compare MS Word documents in the same way we compare source code.


Rhino Mocks 3.5 Broke Our VS2005 Build

February 25, 2009 01:12 by admin

Well, more accurately, I broke the build because I introduced Rhino Mocks 3.5!


Creating a RESTful Web Service Using ASP.Net MVC Part 16 – XML Encoding

February 21, 2009 01:04 by admin

Jim Solderitsch wrote to me asking for helping making the last version of the web service return XML encoded using UTF-8 rather than UTF-16. He couldn’t load the XML returned from the web service into an XmlDocument without an exception being thrown.

I thought this would be simple, but then I’ve not paid much attention to encoding before!


Creating a RESTful Web Service Using ASP.Net MVC Part 15 – Adding Connectedness to JSON

January 25, 2009 01:29 by admin

At the end of my last post about adding connectedness to our web service I had added support for XHTML and XML representations. This allowed us to inject URIs into the representation without changing our Model classes. This was relatively simple because, for those representations, we had stuck to the principle introduced in Multiple Representations of having a transformation layer between internal and external representations of our entities. In this post I want to tackle JSON representations.


Creating a RESTful Web Service Using ASP.Net MVC Part 14 – Connectedness

December 31, 2008 15:33 by admin

In their book RESTful Web Services, Leonard Richardson and Sam Ruby take Roy Fielding’s phrase ”hypermedia as the engine of application state” and explain that it means that the responsibility for tracking and changing application state lies with the client rather than the server. The server indicates how the client can change the application state by providing URIs that point to other possible states. The phrase they prefer to use in place of Roy Fielding’s phrase is “Connectedness.”


Configuring Windows XP to Allow Non-Administrators to Debug ASP.Net

December 18, 2008 23:43 by Admin

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.


Creating a RESTful Web Service Using ASP.Net MVC Part 13 – Round up so far

December 12, 2008 01:01 by admin

In this entry I would like to round up where we have got to so far with this web service. Over the last 13 posts we have developed a fairly functional web service that sticks pretty much to the ideas presented in Leonard Richardson and Sam Ruby’s book RESTful Web Services. It is developed using C# using the (currently Beta) MVC framework from Microsoft that extends the ASP.Net framework.

As an aside, I’ve also taken on board a comment from Stephan and moved some of the reusable classes into their own assembly.


Creating a RESTful Web Service Using ASP.Net MVC Part 12 – Creating a Resource With POST

December 5, 2008 00:55 by admin

Now we can create a resource from an incoming XHTML representation, it is time to accept a representation of a new resource via an HTTP POST. This should be pretty much the same as accepting a new resource via an HTTP PUT.

So what is the difference between a PUT request and a POST request? A PUT request is made directly to the URI of the new resource, the client dictates the URI. A POST request is made to the URI of the new resource’s “parent” URI, the server decides on the full URI of new resource.


Creating a RESTful Web Service Using ASP.Net MVC Part 11 – Supporting Incoming XHTML

November 21, 2008 01:05 by admin

In my last post we added functionality to the web service to accept incoming representations in the form of a PUT request. At the end of that post I admitted I hadn’t implemented the functionality to accept an incoming XHTML representation. The problem was with parsing a string of XHTML using .Net’s built in XML parsers. Loading XHTML straight into an XmlReader causes either an, “An error has occurred while opening external DTD” or a, “Reference to undeclared entity” exception.

In this post we’ll crack that problem.