<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/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>Linq to LLBLGen Pro: feature highlights, part 2</title><link>http://weblogs.asp.net/fbouma/archive/2008/07/03/linq-to-llblgen-pro-feature-highlights-part-2.aspx</link><description>In the first part of this series I talked about the fact that Linq to LLBLGen Pro is a full implementation of Linq and why it's so important to use a full linq provider instead of a half-baked one. Today, I'll discuss a couple of native LLBLGen Pro features</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: Linq to LLBLGen Pro: feature highlights, part 2</title><link>http://weblogs.asp.net/fbouma/archive/2008/07/03/linq-to-llblgen-pro-feature-highlights-part-2.aspx#6447908</link><pubDate>Sun, 27 Jul 2008 00:16:53 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6447908</guid><dc:creator>Steve Macdonald</dc:creator><author>Steve Macdonald</author><description>&lt;p&gt;Brilliant. I read this very carefully. I&amp;#39;m finally starting to appreciate the power of llblgen with LINQ.&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6447908" width="1" height="1"&gt;</description></item></channel></rss>