<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: JSON Serializers In .NET</title>
	<atom:link href="http://aleembawany.com/2009/05/22/json-serializers-in-net/feed/" rel="self" type="application/rss+xml" />
	<link>http://aleembawany.com/2009/05/22/json-serializers-in-net/</link>
	<description>tech, web and the rest</description>
	<lastBuildDate>Thu, 22 Jul 2010 10:20:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Muhammad Qasim Pasta</title>
		<link>http://aleembawany.com/2009/05/22/json-serializers-in-net/comment-page-1/#comment-28179</link>
		<dc:creator>Muhammad Qasim Pasta</dc:creator>
		<pubDate>Thu, 11 Jun 2009 19:31:45 +0000</pubDate>
		<guid isPermaLink="false">http://aleembawany.com/?p=696#comment-28179</guid>
		<description>&lt;p&gt;I downloaded JSON 2.0 but it is also for 3.5 (LINQ :S). However, I tested latest build of JSON.Net  for .Net 2.0 websites and basic functions are working properly without any hustle. But I am not sure whether its a good idea or not...  btw, thanks for wonderful post! :)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I downloaded JSON 2.0 but it is also for 3.5 (LINQ :S). However, I tested latest build of JSON.Net  for .Net 2.0 websites and basic functions are working properly without any hustle. But I am not sure whether its a good idea or not&#8230;  btw, thanks for wonderful post! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aleem</title>
		<link>http://aleembawany.com/2009/05/22/json-serializers-in-net/comment-page-1/#comment-28177</link>
		<dc:creator>Aleem</dc:creator>
		<pubDate>Thu, 11 Jun 2009 17:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://aleembawany.com/?p=696#comment-28177</guid>
		<description>&lt;p&gt;Have you looked at &lt;a href=&quot;http://json.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=13099&quot; rel=&quot;nofollow&quot;&gt;JSON.NET 2.0&lt;/a&gt;? It&#039;s an older release but it&#039;s still a good one. Other than that I am afraid, I have no idea about solutions for .NET 2.0. You could try asking the community over at &lt;a href=&quot;http://stackoverflow.com/&quot; rel=&quot;nofollow&quot;&gt;stackoverflow.com&lt;/a&gt;.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Have you looked at <a href="http://json.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=13099" rel="nofollow">JSON.NET 2.0</a>? It&#8217;s an older release but it&#8217;s still a good one. Other than that I am afraid, I have no idea about solutions for .NET 2.0. You could try asking the community over at <a href="http://stackoverflow.com/" rel="nofollow">stackoverflow.com</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Muhammad Qasim Pasta</title>
		<link>http://aleembawany.com/2009/05/22/json-serializers-in-net/comment-page-1/#comment-28176</link>
		<dc:creator>Muhammad Qasim Pasta</dc:creator>
		<pubDate>Thu, 11 Jun 2009 16:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://aleembawany.com/?p=696#comment-28176</guid>
		<description>&lt;p&gt;Aleem, what if someone don&#039;t want to use .Net 3.5 and still want to use JSON? I checked out Json.Net but their latest build is for framework 3.5. there are some other parser but most of them with GPL license :S ... any advice?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Aleem, what if someone don&#8217;t want to use .Net 3.5 and still want to use JSON? I checked out Json.Net but their latest build is for framework 3.5. there are some other parser but most of them with GPL license :S &#8230; any advice?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->