<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>.NET Framework: What do you use?</title><link>http://blogs.msdn.com/brada/archive/2008/10/13/net-framework-what-do-you-use.aspx</link><description>One of the common things we discuss on the .NET Framework prod uct team is around the popularity of different features of the .NET Framework. We have some very interesting semi-scientific methods for gathering data like this, but Hanselman and I thought</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: .NET Framework: What do you use?</title><link>http://blogs.msdn.com/brada/archive/2008/10/13/net-framework-what-do-you-use.aspx#9001414</link><pubDate>Thu, 16 Oct 2008 07:18:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9001414</guid><dc:creator>Keith Hill</dc:creator><description>&lt;p&gt;I would suggest a couple of separate entries to LINQ: LINQ to SQL (I don't use), LINQ to Objects and LINQ to XML, both of which I use and really like.&lt;/p&gt;
</description></item></channel></rss>