<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">ASP.NET AJAX Team Blogs</title><subtitle type="html" /><id>http://weblogs.asp.net/atlas-team/atom.aspx</id><link rel="alternate" type="text/html" href="http://weblogs.asp.net/atlas-team/default.aspx" /><link rel="self" type="application/atom+xml" href="http://weblogs.asp.net/atlas-team/atom.aspx" /><generator uri="http://communityserver.org" version="3.0.20510.895">Community Server</generator><updated>2009-08-22T13:35:45Z</updated><entry><title>JavaScript class browser: once again with jQuery</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/bleroy/archive/2009/10/30/javascript-class-browser-once-again-with-jquery.aspx" /><id>http://weblogs.asp.net/bleroy/archive/2009/10/30/javascript-class-browser-once-again-with-jquery.aspx</id><published>2009-10-30T17:43:26Z</published><updated>2009-10-30T17:43:26Z</updated><content type="html">I’ve already posted twice about that little class browser application. The first iteration was mostly declarative and can be found here: http://weblogs.asp.net/bleroy/archive/2009/09/14/building-a-class-browser-with-microsoft-ajax-4-0-preview-5.aspx The second one was entirely imperative and can be found here: http://weblogs.asp.net/bleroy/archive/2009/10/15/entirely-unobtrusive-and-imperative-templates-with-microsoft-ajax-4-preview-6.aspx This new version builds on top of the code for the imperative...(&lt;a href="http://weblogs.asp.net/bleroy/archive/2009/10/30/javascript-class-browser-once-again-with-jquery.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7243407" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="JavaScript" scheme="http://weblogs.asp.net/atlas-team/archive/tags/JavaScript/default.aspx" /><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="Atlas" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Atlas/default.aspx" /><category term="HTML" scheme="http://weblogs.asp.net/atlas-team/archive/tags/HTML/default.aspx" /><category term="jQuery" scheme="http://weblogs.asp.net/atlas-team/archive/tags/jQuery/default.aspx" /><category term="Microsoft AJAX Library" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Microsoft+AJAX+Library/default.aspx" /></entry><entry><title>How to render the same template on the server and client with minimal redundancy</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/bleroy/archive/2009/10/19/how-to-render-the-same-template-on-the-server-and-client-with-minimal-redundancy.aspx" /><id>http://weblogs.asp.net/bleroy/archive/2009/10/19/how-to-render-the-same-template-on-the-server-and-client-with-minimal-redundancy.aspx</id><published>2009-10-19T08:50:00Z</published><updated>2009-10-19T08:50:00Z</updated><content type="html">Last week, I wrote a post about how the new Microsoft Ajax Library Preview 6 made it a lot easier to write unobtrusive and imperative data-driven applications . Because for the previous preview, I had written a cool little class browser using a declarative style, I thought it would be nice to rewrite this in a completely imperative way. The mistake I made though was to call it unobtrusive. Never mind that ‘unobtrusive’ is a perfectly well-defined word that actually existed way before JavaScript....(&lt;a href="http://weblogs.asp.net/bleroy/archive/2009/10/19/how-to-render-the-same-template-on-the-server-and-client-with-minimal-redundancy.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7232879" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="JavaScript" scheme="http://weblogs.asp.net/atlas-team/archive/tags/JavaScript/default.aspx" /><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="Atlas" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Atlas/default.aspx" /><category term="HTML" scheme="http://weblogs.asp.net/atlas-team/archive/tags/HTML/default.aspx" /><category term="Microsoft AJAX Library" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Microsoft+AJAX+Library/default.aspx" /></entry><entry><title>Announcing Microsoft Ajax Library (Preview 6) and the Microsoft Ajax Minifier</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/scottgu/archive/2009/10/15/announcing-microsoft-ajax-library-preview-6-and-the-microsoft-ajax-minifier.aspx" /><id>http://weblogs.asp.net/scottgu/archive/2009/10/15/announcing-microsoft-ajax-library-preview-6-and-the-microsoft-ajax-minifier.aspx</id><published>2009-10-16T06:48:09Z</published><updated>2009-10-16T06:48:09Z</updated><content type="html">The ASP.NET team today released a significant new update of the Microsoft Ajax Library (Preview 6).&amp;#160; This update includes a bunch of new capabilities and improvements to our client-side AJAX library, and can be used with any version of ASP.NET (including ASP.NET 2.0, 3.5 and 4.0), and can be used in both ASP.NET Web Forms and ASP.NET MVC projects.&amp;#160; Today’s release includes the following feature improvements: Better Imperative Syntax : A new, simplified, code syntax for creating client controls...(&lt;a href="http://weblogs.asp.net/scottgu/archive/2009/10/15/announcing-microsoft-ajax-library-preview-6-and-the-microsoft-ajax-minifier.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7231171" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term=".NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/.NET/default.aspx" /><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="Atlas" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Atlas/default.aspx" /><category term="Community News" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Community+News/default.aspx" /><category term="Visual Studio" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Visual+Studio/default.aspx" /></entry><entry><title>Entirely unobtrusive and imperative templates with Microsoft Ajax Library Preview 6</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/bleroy/archive/2009/10/15/entirely-unobtrusive-and-imperative-templates-with-microsoft-ajax-4-preview-6.aspx" /><id>http://weblogs.asp.net/bleroy/archive/2009/10/15/entirely-unobtrusive-and-imperative-templates-with-microsoft-ajax-4-preview-6.aspx</id><published>2009-10-15T09:12:00Z</published><updated>2009-10-15T09:12:00Z</updated><content type="html">Today is the release of the sixth preview of Microsoft Ajax Library. Don’t get fooled by the somewhat silly and long name: this is a major release in many ways. The scripts have been majorly refactored since preview 5. Check out the other posts out there (links at the bottom of this post) to see just some of the many new features that are in there. Some of my favorite are all the small improvements that have been made to make imperative instantiation of components and templated contents easier than...(&lt;a href="http://weblogs.asp.net/bleroy/archive/2009/10/15/entirely-unobtrusive-and-imperative-templates-with-microsoft-ajax-4-preview-6.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7231198" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="JavaScript" scheme="http://weblogs.asp.net/atlas-team/archive/tags/JavaScript/default.aspx" /><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="Atlas" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Atlas/default.aspx" /><category term="HTML" scheme="http://weblogs.asp.net/atlas-team/archive/tags/HTML/default.aspx" /><category term="jQuery" scheme="http://weblogs.asp.net/atlas-team/archive/tags/jQuery/default.aspx" /><category term="Microsoft AJAX Library" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Microsoft+AJAX+Library/default.aspx" /></entry><entry><title>Ajax Control Toolkit: new controls, bug fixes</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/bleroy/archive/2009/09/30/ajax-control-toolkit-new-controls-bug-fixes.aspx" /><id>http://weblogs.asp.net/bleroy/archive/2009/09/30/ajax-control-toolkit-new-controls-bug-fixes.aspx</id><published>2009-10-01T00:28:59Z</published><updated>2009-10-01T00:28:59Z</updated><content type="html">And we have a new release of Ajax Control Toolkit. I didn’t work on this one but there are some nice things in there nonetheless :) First, new controls! SeaDragon : I’ve blogged before about Seadragon , the JavaScript-only way to do Deep Zoom . It became a lot easier to use a few month ago when the need for tools disappeared and you can just point to any image on the web and immediately get the URL and script tag to put on your page: Now with this release of Ajax Control Toolkit, including and controlling...(&lt;a href="http://weblogs.asp.net/bleroy/archive/2009/09/30/ajax-control-toolkit-new-controls-bug-fixes.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7220985" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="AJAX Control Toolkit" scheme="http://weblogs.asp.net/atlas-team/archive/tags/AJAX+Control+Toolkit/default.aspx" /><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="CodePlex" scheme="http://weblogs.asp.net/atlas-team/archive/tags/CodePlex/default.aspx" /><category term="Deep Zoom" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Deep+Zoom/default.aspx" /><category term="Microsoft AJAX Library" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Microsoft+AJAX+Library/default.aspx" /></entry><entry><title>Fluent API for .NET RIA Services Metadata</title><link rel="alternate" type="text/html" href="http://www.nikhilk.net/RIA-Services-Fluent-Metadata-API.aspx" /><id>http://www.nikhilk.net/RIA-Services-Fluent-Metadata-API.aspx</id><published>2009-09-21T04:34:10Z</published><updated>2009-09-21T04:34:10Z</updated><content type="html">.NET RIA Services relies heavily on metadata annotations for expressing intent beyond what can be inferrd via convention. For example, validation rules on entities and members can be declared as annotations, which then enable a variety of consumption scenarios. We also have metadata for describing model aspects in DAL-agnostic fashion, and hints for automatic UI-generation. What we have today is just a first step. The general design we&amp;#39;re enabling is actually quite flexible. For example, a number...(&lt;a href="http://www.nikhilk.net/RIA-Services-Fluent-Metadata-API.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7212583" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="Silverlight" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Silverlight/default.aspx" /></entry><entry><title>Announcing the Microsoft AJAX CDN</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/scottgu/archive/2009/09/15/announcing-the-microsoft-ajax-cdn.aspx" /><id>http://weblogs.asp.net/scottgu/archive/2009/09/15/announcing-the-microsoft-ajax-cdn.aspx</id><published>2009-09-16T06:46:17Z</published><updated>2009-09-16T06:46:17Z</updated><content type="html">Earlier today the ASP.NET team launched a new Microsoft Ajax CDN (Content Delivery Network) service that provides caching support for AJAX libraries (including jQuery and ASP.NET AJAX).&amp;#160; The service is available for free, does not require any registration, and can be used for both commercial and non-commercial purposes. What does a CDN provide? Content delivery networks (CDNs) are composed of &amp;quot;edge cache&amp;quot; servers that are strategically placed around the world at key Internet network...(&lt;a href="http://weblogs.asp.net/scottgu/archive/2009/09/15/announcing-the-microsoft-ajax-cdn.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7207651" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term=".NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/.NET/default.aspx" /><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="Atlas" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Atlas/default.aspx" /><category term="Community News" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Community+News/default.aspx" /><category term="Visual Studio" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Visual+Studio/default.aspx" /></entry><entry><title>Building a class browser with Microsoft Ajax 4.0 Preview 5</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/bleroy/archive/2009/09/14/building-a-class-browser-with-microsoft-ajax-4-0-preview-5.aspx" /><id>http://weblogs.asp.net/bleroy/archive/2009/09/14/building-a-class-browser-with-microsoft-ajax-4-0-preview-5.aspx</id><published>2009-09-14T07:29:37Z</published><updated>2009-09-14T07:29:37Z</updated><content type="html">The Microsoft Ajax Library 4.0 Preview 5 is the first release of Microsoft Ajax that I didn’t participate in: I left the team a few months ago. But that doesn’t mean I don’t love what’s in there, and I really do. And by the way I’ve also seen what’s in Preview 6 too and man that will seriously rock. So I thought I’d write a little something to celebrate the new preview. The new features include recursive templates, which is pretty much begging us to implement a treeview with it, and we’ll do just...(&lt;a href="http://weblogs.asp.net/bleroy/archive/2009/09/14/building-a-class-browser-with-microsoft-ajax-4-0-preview-5.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7204722" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="Atlas" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Atlas/default.aspx" /><category term="HTML" scheme="http://weblogs.asp.net/atlas-team/archive/tags/HTML/default.aspx" /><category term="Microsoft AJAX Library" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Microsoft+AJAX+Library/default.aspx" /></entry><entry><title>Dialogs and ViewModel - Using Tasks as a Pattern</title><link rel="alternate" type="text/html" href="http://www.nikhilk.net/ViewModel-Dialogs-Task-Pattern.aspx" /><id>http://www.nikhilk.net/ViewModel-Dialogs-Task-Pattern.aspx</id><published>2009-09-11T16:37:28Z</published><updated>2009-09-11T16:37:28Z</updated><content type="html">The ViewModel/MVVM pattern continues to gain popularity, with a blog post showing up every so often, and with tweets and retweets popping up even more often :-). At the same time, there are some interesting topics beyond the core pattern that continue to fuel experimentation. A big one amongst those is how should applications use dialogs when using the view model pattern. The crux of the problem is the desire to keep the view model independent of UI concerns, and ensure it can be tested in a standalone...(&lt;a href="http://www.nikhilk.net/ViewModel-Dialogs-Task-Pattern.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7201131" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="Silverlight" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Silverlight/default.aspx" /></entry><entry><title>Doloto - AJAX application optimization tool</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/publicsector/archive/2009/09/08/doloto-ajax-application-optimization-tool.aspx" /><id>http://blogs.msdn.com/publicsector/archive/2009/09/08/doloto-ajax-application-optimization-tool.aspx</id><published>2009-09-08T14:52:00Z</published><updated>2009-09-08T14:52:00Z</updated><content type="html">&amp;quot;Doloto reduces the size of initial application code download by hundreds of kilobytes or as much as 50% of the original download size. The time to download and begin interacting with large applications is reduced by 20-40% or dozens of seconds as shown below, depending on the application and wide-area network conditions.&amp;quot; http://msdn.microsoft.com/en-us/devlabs/ee423534.aspx Rock with it! - Keith Read More......(&lt;a href="http://blogs.msdn.com/publicsector/archive/2009/09/08/doloto-ajax-application-optimization-tool.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7197560" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="Ajax" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Ajax/default.aspx" /></entry><entry><title>querySelectorAll on old IE versions: something that doesn’t work</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/bleroy/archive/2009/08/31/queryselectorall-on-old-ie-versions-something-that-doesn-t-work.aspx" /><id>http://weblogs.asp.net/bleroy/archive/2009/08/31/queryselectorall-on-old-ie-versions-something-that-doesn-t-work.aspx</id><published>2009-09-01T01:03:13Z</published><updated>2009-09-01T01:03:13Z</updated><content type="html">In today’s post, I’m going to show an interesting technique to solve a problem and then I will tear it to pieces and explain why it is actually useless. I believe that negative results should also be published so that we can save other people from wasting time trying the same thing. So here goes… A few days ago, a post on Ajaxian proposed a new version of a somewhat old technique to implement querySelectorAll on old versions of IE, using the browser’s native CSS engine. That sounds like a great idea...(&lt;a href="http://weblogs.asp.net/bleroy/archive/2009/08/31/queryselectorall-on-old-ie-versions-something-that-doesn-t-work.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7187194" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="JavaScript" scheme="http://weblogs.asp.net/atlas-team/archive/tags/JavaScript/default.aspx" /><category term="ASP.NET" scheme="http://weblogs.asp.net/atlas-team/archive/tags/ASP.NET/default.aspx" /><category term="CSS" scheme="http://weblogs.asp.net/atlas-team/archive/tags/CSS/default.aspx" /><category term="Internet Explorer" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Internet+Explorer/default.aspx" /><category term="jQuery" scheme="http://weblogs.asp.net/atlas-team/archive/tags/jQuery/default.aspx" /><category term="Microsoft AJAX Library" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Microsoft+AJAX+Library/default.aspx" /><category term="TwitCode" scheme="http://weblogs.asp.net/atlas-team/archive/tags/TwitCode/default.aspx" /></entry><entry><title>Photos from Death Valley</title><link rel="alternate" type="text/html" href="http://www.nikhilk.net/Death-Valley.aspx" /><id>http://www.nikhilk.net/Death-Valley.aspx</id><published>2009-08-29T14:57:01Z</published><updated>2009-08-29T14:57:01Z</updated><content type="html">[ Full post continued here... ] Read More......(&lt;a href="http://www.nikhilk.net/Death-Valley.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7185122" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="Photography" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Photography/default.aspx" /></entry><entry><title>BouncingPlane Behavior for Silverlight</title><link rel="alternate" type="text/html" href="http://www.nikhilk.net/BouncingPlane-Behavior.aspx" /><id>http://www.nikhilk.net/BouncingPlane-Behavior.aspx</id><published>2009-08-27T23:15:22Z</published><updated>2009-08-27T23:15:22Z</updated><content type="html">Time for a brief but fun post... some time back Tim Heuer posted the Silverlight 3 bouncing plane gratuitous demo . Click an element, and the nearest corner would bounce backwards and forwards as it comes back to rest. Tim had the code to setup the storyboards, and handle the mouse interaction in code-behind. I look at it, and immediately see a reusable component (even if it is a gratuitous one), or more specifically a behavior, that encapsulates all the logic, and can be attached declaratively in...(&lt;a href="http://www.nikhilk.net/BouncingPlane-Behavior.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7183487" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="Silverlight" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Silverlight/default.aspx" /></entry><entry><title>LINQ to Bing, Silverlight and .NET RIA Services</title><link rel="alternate" type="text/html" href="http://www.nikhilk.net/BLinq-Silverlight-RIAServices.aspx" /><id>http://www.nikhilk.net/BLinq-Silverlight-RIAServices.aspx</id><published>2009-08-26T18:20:20Z</published><updated>2009-08-26T18:20:20Z</updated><content type="html">In my last post, I described BLinq, or LINQ to Bing , an API that allows you use LINQ to access the Bing search results (ok, so perhaps BLinq was not the best of names, given prior art on that name ... but anyway). I also alluded to .NET RIA Services integration, which I&amp;#39;ll cover in this installment. In fact, IQueryable and the LINQ pattern lie at the very heart of .NET RIA Services, in allowing developers to access data in a consistent manner not just on client or server but across client and...(&lt;a href="http://www.nikhilk.net/BLinq-Silverlight-RIAServices.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7182214" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="Silverlight" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Silverlight/default.aspx" /></entry><entry><title>BLinq - Linq to Bing Search APIs</title><link rel="alternate" type="text/html" href="http://www.nikhilk.net/BLinq-LINQ-over-Bing.aspx" /><id>http://www.nikhilk.net/BLinq-LINQ-over-Bing.aspx</id><published>2009-08-22T17:35:45Z</published><updated>2009-08-22T17:35:45Z</updated><content type="html">As part of validating and playing with some of the extensibility features in .NET RIA Services, I needed to write a LINQ provider. This was also a good opportunity to delve into some of the deeper technical aspects of the IQueryable construct, expression trees and related concepts, which I had not gotten into first-hand until now. For my prototyping, I decided to write a LINQ provider for querying Bing to search for pages and images. This post will focus on using the LINQ provider itself, and seeing...(&lt;a href="http://www.nikhilk.net/BLinq-LINQ-over-Bing.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7177969" width="1" height="1"&gt;</content><author><name>Anonymous</name><uri>http://weblogs.asp.net/members/Anonymous.aspx</uri></author><category term="Projects" scheme="http://weblogs.asp.net/atlas-team/archive/tags/Projects/default.aspx" /></entry></feed>