<?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: LINQ to FILE Provider</title>
	<atom:link href="http://clarionsharp.com/blog/2009/09/linq-to-file-provider/feed/" rel="self" type="application/rss+xml" />
	<link>http://clarionsharp.com/blog/2009/09/linq-to-file-provider/</link>
	<description>Simply the fastest tool available for creating custom database applications!</description>
	<pubDate>Mon, 06 Sep 2010 10:30:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeff Slarve</title>
		<link>http://clarionsharp.com/blog/2009/09/linq-to-file-provider/comment-page-1/#comment-62</link>
		<dc:creator>Jeff Slarve</dc:creator>
		<pubDate>Tue, 08 Sep 2009 16:59:52 +0000</pubDate>
		<guid isPermaLink="false">http://clarionsharp.com/blog/?p=206#comment-62</guid>
		<description>Thanks Robert</description>
		<content:encoded><![CDATA[<p>Thanks Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rzaunere</title>
		<link>http://clarionsharp.com/blog/2009/09/linq-to-file-provider/comment-page-1/#comment-60</link>
		<dc:creator>rzaunere</dc:creator>
		<pubDate>Sun, 06 Sep 2009 16:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://clarionsharp.com/blog/?p=206#comment-60</guid>
		<description>No LINQ is not deprecated by MS, it shipped in .Net 3.5 and its included as part of .Net 4. What did happen is that the MS ADO.Net team is now stating that the new (still in beta) Entity Framework (EF) will be the MS recommended data access approach.  But if the Entity Framework does actually work out then no worries for LINQ, as there is a LINQ to Entities provider which consumes the objects created by the EF. Of course none of the MS insider battle over data access frameworks matters at all if you're using the new LINQ to FILE provider.</description>
		<content:encoded><![CDATA[<p>No LINQ is not deprecated by MS, it shipped in .Net 3.5 and its included as part of .Net 4. What did happen is that the MS ADO.Net team is now stating that the new (still in beta) Entity Framework (EF) will be the MS recommended data access approach.  But if the Entity Framework does actually work out then no worries for LINQ, as there is a LINQ to Entities provider which consumes the objects created by the EF. Of course none of the MS insider battle over data access frameworks matters at all if you&#8217;re using the new LINQ to FILE provider.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blogengine.NET Extension : Silverlight Extension - CODE - Random Things To Blog</title>
		<link>http://clarionsharp.com/blog/2009/09/linq-to-file-provider/comment-page-1/#comment-59</link>
		<dc:creator>Blogengine.NET Extension : Silverlight Extension - CODE - Random Things To Blog</dc:creator>
		<pubDate>Sat, 05 Sep 2009 19:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://clarionsharp.com/blog/?p=206#comment-59</guid>
		<description>[...] Clarion » Blog Archive » LINQ to FILE Provider [...]</description>
		<content:encoded><![CDATA[<p>[...] Clarion » Blog Archive » LINQ to FILE Provider [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Slarve</title>
		<link>http://clarionsharp.com/blog/2009/09/linq-to-file-provider/comment-page-1/#comment-58</link>
		<dc:creator>Jeff Slarve</dc:creator>
		<pubDate>Fri, 04 Sep 2009 20:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://clarionsharp.com/blog/?p=206#comment-58</guid>
		<description>I've read some stuff about LINQ being deprecated by MS. Is this not the case?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve read some stuff about LINQ being deprecated by MS. Is this not the case?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
