What a great idea! A lot of companies create custom error pages so that you don’t see the ugly, default error page that comes with the web server that runs their site. When I say ugly, I mean… UGLY.

Many of them style it to look like their site so that there is consistency in the site.

I stumbled upon this awesome idea from Scott Hanselman that is not only a good idea, but easy to implement. Click on through to the article to learn how to put your error pages to work for good. And always, if you need help getting this into YOUR website, give Dash Technical Solutions a call and we’ll do our best to help you out!

Put Missing Kids on your 404 Page - Entirely Client-Side Solution with YQL, jQuery, and MSAjax

More for my own sake than anything else I thought I would comment on this article… This is a good post that details how to create  JSON Web Service with .NET technologies.

JSON (short for JavaScript Object Notation and pronounced like “Jason”) is catching on quickly with developers due to the fact that:

• JSON is easy
• JSON is nothing more than name : value pairs assigned within an object
• JSON is easy to understand because if written well, it’s a self-documenting structure.
• JSON is fast (parsing is extremely efficient)
• JSON organizes the ugly mess of procedural programming

An example of a JSON object:

{    
    "name": "Jack (\"Bee\") Nimble",     
    "format": {
         "type":       "rect",
         "width":      1920,
         "height":     1080,
         "interlace":  false,
         "frame rate": 24
    }
}

From my seat, this is a lot easier to understand than SOAP (Simple Object Access Protocol) that has been the standard for .NET Web Services ever since I can remember…

But also an interesting read is The Limitations of JSON, so it’s not a silver bullet.

How To Create A JSON Web Service In ASP.NET – Williamsport Web Developer Weblog