<?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>LINQ Design Guidelines</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx</link><description>Mircea, a program manager on my team, has worked on development of design guidelines for LINQ related features . The guidelines were reviewed internally and are now available on Mitch’s blog. We might still iterate on them a bit, but quite soon I plan</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: LINQ Design Guidelines</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx#8178864</link><pubDate>Thu, 13 Mar 2008 08:34:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8178864</guid><dc:creator>Keith Patrick</dc:creator><description>&lt;p&gt;Thank you for just referring to lambda expressions as a shorthand for anonymous delegates. It drove me nuts trying to grasp the concept early on due to all the space dedicated to the origins in calculus (it served to confuse more than inform). In fact, that goes for a lot of these guidelines; I would have saved a bit of time/frustration if these were around a few months ago rather than the long drawn out MSDN articles introducing LINQ. &amp;nbsp;Straight and to the point is great (lamdbas are delegates, LINQ is a bunch of extension methods, the nature of Expression&amp;lt;&amp;gt;.&lt;/p&gt;
&lt;p&gt;One thing, though: for us language purists, could you include alternate method call versions of sample code instead of just the language extensions? I find the not-quite-SQL format of the LI part to be more confusing than helpful due to the odd structuring of the SELECTs&lt;/p&gt;</description></item><item><title>re: LINQ Design Guidelines</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx#8179748</link><pubDate>Thu, 13 Mar 2008 12:24:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8179748</guid><dc:creator>Kent Boogaart</dc:creator><description>&lt;p&gt;Don't seem to be able to comment against that post so I'll post here...&lt;/p&gt;
&lt;p&gt;Just wondering whether there should be explicit treatment of extension methods against enumerations in the guidelines. It seems to me that it will be quite common to see something like:&lt;/p&gt;
&lt;p&gt;public enum MyEnum {&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;ValueOne, ValueTwo&lt;/p&gt;
&lt;p&gt;}&lt;/p&gt;
&lt;p&gt;public static class MyEnumExtensions {&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;public static string ToHumanReadableString(this MyEnum myEnum) {&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;//impl&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;}&lt;/p&gt;
&lt;p&gt;}&lt;/p&gt;
&lt;p&gt;According to the guidelines, this is bad because the extensions are in the same namespace as the enumeration. But is it really such a bad thing for enumerations? They're a special case, IMO - these members cannot be added directly to them.&lt;/p&gt;</description></item><item><title>LINQ Design Guidelines</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx#8179773</link><pubDate>Thu, 13 Mar 2008 12:34:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8179773</guid><dc:creator>Andrejs Mamontovs</dc:creator><description>&lt;p&gt;Krzysztof Cwalina savā vietnē ( &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx"&gt;http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx&lt;/a&gt; ) paziņojis&lt;/p&gt;
</description></item><item><title>New and Notable 226</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx#8180524</link><pubDate>Thu, 13 Mar 2008 16:33:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8180524</guid><dc:creator>Sam Gentile</dc:creator><description>&lt;p&gt;&amp;amp;#160; Comments and trackbacks are back on after a futile battle with spam. I&amp;amp;#39;ll see how long it&lt;/p&gt;
</description></item><item><title>LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx#8197530</link><pubDate>Fri, 14 Mar 2008 10:36:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8197530</guid><dc:creator>Community Blogs</dc:creator><description>&lt;p&gt;You know that I&amp;amp;#39;m a big fan of framework and library design so also have been a big fan of Framework&lt;/p&gt;
</description></item><item><title>Visual Studio Team System 2008 Development Edition with MSDN Premium Subscription</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx#9399222</link><pubDate>Thu, 05 Feb 2009 20:31:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9399222</guid><dc:creator>Termékinformációk fejlesztőknek</dc:creator><description>&lt;p&gt;[ Nacsa S&amp;#225;ndor , 2009. janu&amp;#225;r 19. – febru&amp;#225;r 5.] Ez a Team System v&amp;#225;ltozat fejlett eszk&amp;#246;zrendszert k&amp;#237;n&amp;#225;l&lt;/p&gt;
</description></item><item><title> Krzysztof Cwalina LINQ Design Guidelines | Outdoor Decor</title><link>http://blogs.msdn.com/kcwalina/archive/2008/03/12/8178467.aspx#9778944</link><pubDate>Fri, 19 Jun 2009 07:16:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9778944</guid><dc:creator> Krzysztof Cwalina LINQ Design Guidelines | Outdoor Decor</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://outdoordecoration.info/story.php?id=1833"&gt;http://outdoordecoration.info/story.php?id=1833&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>