<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://professionalaspnet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Using JQuery and JSON to Interact with a WCF Service via AJAX</title><link>http://professionalaspnet.com/archive/2010/02/08/Using-JQuery-and-JSON-to-Interact-with-a-WCF-Service-via-AJAX.aspx</link><description>Yesterday’s post reviewed how to setup a WCF web service to work with JSON from top to bottom. Today I am going to review what needs to be done to use JQuery to work with those WCF end points. If you have not already done so please download the example</description><dc:language>en</dc:language><generator>CommunityServer 2.1 (Build: 60809.935)</generator><item><title>re: Using JQuery and JSON to Interact with a WCF Service via AJAX</title><link>http://professionalaspnet.com/archive/2010/02/08/Using-JQuery-and-JSON-to-Interact-with-a-WCF-Service-via-AJAX.aspx#69073</link><pubDate>Mon, 08 Feb 2010 17:52:19 GMT</pubDate><guid isPermaLink="false">9f8c9708-cda3-4e3e-8e5b-ee2a54f50e19:69073</guid><dc:creator>Roger Pence</dc:creator><description>Chris--

WCF seems like a giant hammer for delivering JSON to the client. In the case you've presented, a RESTful solution seems more appropriate. I appreciate the need to call WCF from the client (and I appreciate your example), but given the problem you've solved, would you really use WCF in practice? 

rp</description></item><item><title>
        Twitter Trackbacks for
         
        Chris Love's Official ASP.NET Blog : Using JQuery and JSON to Interact with a WCF Service via AJAX 
        [professionalaspnet.com]
        on Topsy.com
    </title><link>http://professionalaspnet.com/archive/2010/02/08/Using-JQuery-and-JSON-to-Interact-with-a-WCF-Service-via-AJAX.aspx#69074</link><pubDate>Mon, 08 Feb 2010 18:09:01 GMT</pubDate><guid isPermaLink="false">9f8c9708-cda3-4e3e-8e5b-ee2a54f50e19:69074</guid><dc:creator>
        Twitter Trackbacks for
         
        Chris Love's Official ASP.NET Blog : Using JQuery and JSON to Interact with a WCF Service via AJAX 
        [professionalaspnet.com]
        on Topsy.com
    </dc:creator><description>PingBack from http://topsy.com/tb/professionalaspnet.com/archive/2010/02/08/Using-JQuery-and-JSON-to-Interact-with-a-WCF-Service-via-AJAX.aspx</description></item><item><title>re: Using JQuery and JSON to Interact with a WCF Service via AJAX</title><link>http://professionalaspnet.com/archive/2010/02/08/Using-JQuery-and-JSON-to-Interact-with-a-WCF-Service-via-AJAX.aspx#69171</link><pubDate>Tue, 09 Feb 2010 12:41:57 GMT</pubDate><guid isPermaLink="false">9f8c9708-cda3-4e3e-8e5b-ee2a54f50e19:69171</guid><dc:creator>Chris Love</dc:creator><description>&lt;p&gt;Roger your point is taken, but when your client does not want to use REST (aka ADO.NET Data Services) your solution will not work ;)&lt;/p&gt;
</description></item><item><title>WCF and jQuery Exception Handling</title><link>http://professionalaspnet.com/archive/2010/02/08/Using-JQuery-and-JSON-to-Interact-with-a-WCF-Service-via-AJAX.aspx#72917</link><pubDate>Thu, 18 Feb 2010 17:37:47 GMT</pubDate><guid isPermaLink="false">9f8c9708-cda3-4e3e-8e5b-ee2a54f50e19:72917</guid><dc:creator>Chris Love's Official ASP.NET Blog</dc:creator><description>&lt;p&gt;Now that I have covered the basics of calling a WCF service using jQuery&amp;amp;rsquo;s AJAX functionality with&lt;/p&gt;
</description></item><item><title>re: Using JQuery and JSON to Interact with a WCF Service via AJAX</title><link>http://professionalaspnet.com/archive/2010/02/08/Using-JQuery-and-JSON-to-Interact-with-a-WCF-Service-via-AJAX.aspx#99602</link><pubDate>Wed, 12 May 2010 00:44:50 GMT</pubDate><guid isPermaLink="false">9f8c9708-cda3-4e3e-8e5b-ee2a54f50e19:99602</guid><dc:creator>Mike M.</dc:creator><description>I appreciate the good info in the post.  But what happens when includeExceptionDetailInFaults is set to false in order to avoid security concerns in production (as recommended by Microsoft)?  Ultimately I'm looking for a good way to get "enough" exception detail back to the browser so that a user can be guided on where to go next.  Any ideas?</description></item></channel></rss>