Comments on: JSON and ASP.NET http://www.itsananderson.com/2009/06/json-and-asp-net/ Designer and Programmer Wed, 10 Mar 2010 16:05:01 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Derek Hammer http://www.itsananderson.com/2009/06/json-and-asp-net/comment-page-1/#comment-309 Derek Hammer Sat, 27 Jun 2009 21:19:46 +0000 http://www.itsananderson.com/?p=626#comment-309 I have a lot of responses to this. A lot of them are going to be negative but don't take that the wrong way. Just constructive criticism / insight. First, ASP.NET has its own Ajax Toolkit. The toolkit itself has some design decisions that I disagree with but it also integrates very well with ASP.NET. For any user that is coding in ASP.NET and wants to AJAX-up their website I would recommend starting with ASP.NET. Also, using the toolkit described about, it would be better to create a JSON control that would handle the situation you described about, if you really wanted JSON. This control would handle all the weird logic that would be associated with the JSON response and abstract it from using it all over the place. Finally, the solution you describe is not very RESTful. I know that this is hard to do in ASP.NET and don't know off the top of my head a good solution to it, which leads to my final point.. I love C# and .NET. But ASP.NET is a real-world example of a hack-and-slash framework. It's useful for the time being and provides a lot of functionality. However, I would recommend shying away from the framework and work toward a Ruby on Rails, Django, Cappuccino, etc. solution. ASP.NET 4.0 seems to be lackluster, too. Good thing that you're looking into a bunch of solutions for these things though! P.S. Add OpenID to your blog so I don't have to sign in :P I have a lot of responses to this. A lot of them are going to be negative but don’t take that the wrong way. Just constructive criticism / insight.

First, ASP.NET has its own Ajax Toolkit. The toolkit itself has some design decisions that I disagree with but it also integrates very well with ASP.NET. For any user that is coding in ASP.NET and wants to AJAX-up their website I would recommend starting with ASP.NET.

Also, using the toolkit described about, it would be better to create a JSON control that would handle the situation you described about, if you really wanted JSON. This control would handle all the weird logic that would be associated with the JSON response and abstract it from using it all over the place.

Finally, the solution you describe is not very RESTful. I know that this is hard to do in ASP.NET and don’t know off the top of my head a good solution to it, which leads to my final point..

I love C# and .NET. But ASP.NET is a real-world example of a hack-and-slash framework. It’s useful for the time being and provides a lot of functionality. However, I would recommend shying away from the framework and work toward a Ruby on Rails, Django, Cappuccino, etc. solution. ASP.NET 4.0 seems to be lackluster, too.

Good thing that you’re looking into a bunch of solutions for these things though!

P.S. Add OpenID to your blog so I don’t have to sign in :P

]]>