<?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 Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx</link><description>Writing applications that interact with data sources, such as databases, XML documents, or Web Services such as Flickr or Amazon, is made easier in the .NET Framework 3.5 with the addition of a set of features collectively referred to as LINQ ( L anguage-</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>LINQ Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8178468</link><pubDate>Thu, 13 Mar 2008 07:16:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8178468</guid><dc:creator>Krzysztof Cwalina</dc:creator><description>&lt;p&gt;Mircea, a program manager on my team, has worked on development of design guidelines for LINQ related&lt;/p&gt;
</description></item><item><title>LINQ Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8178708</link><pubDate>Thu, 13 Mar 2008 07:59:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8178708</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;Mircea, a program manager on my team, has worked on development of design guidelines for LINQ related&lt;/p&gt;
</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8178775</link><pubDate>Thu, 13 Mar 2008 08:09:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8178775</guid><dc:creator>kfarmer@microsoft.com</dc:creator><description>&lt;p&gt;One thing I've been considering is reducing classes to their basics: &amp;nbsp;pretty much just properties, methods directly relevant to those properties, and constructors and convertors.&lt;/p&gt;
&lt;p&gt;Then use extension methods to define operations that are, pretty much, not required to mantain the concept of the class as an entity in itself, and where it doesn't make sense to create a subtype (if a subtype is even possible).&lt;/p&gt;
&lt;p&gt;For example, a Node exists just fine without knowing about operations over Graph&amp;lt;Node&amp;gt;, and arguably Graph&amp;lt;Node&amp;gt; need not have any knowledge about IsNetworkRouter.&lt;/p&gt;
&lt;p&gt;In that case, something like Traverse(GraphLink&amp;lt;Node&amp;gt;) would be a great method method on Graph&amp;lt;Node&amp;gt;, but something like FindLeastWorkRoute(Node, Node), which depends on implementation details of the particular subtype of GraphLink (ie, it has an associated Work metric) would best be an extension method in my mind.&lt;/p&gt;
&lt;p&gt;This is a way to avoid creating custom subtypes just to implement application-specific logic, and thereby cluttering up the interesting classes (eg, Graph, rather than both Graph and GraphLink).&lt;/p&gt;
</description></item><item><title>LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8179669</link><pubDate>Thu, 13 Mar 2008 11:56:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8179669</guid><dc:creator>DotNetKicks.com</dc:creator><description>&lt;p&gt;You've been kicked (a good thing) - Trackback from DotNetKicks.com&lt;/p&gt;
</description></item><item><title>LINQ Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8179774</link><pubDate>Thu, 13 Mar 2008 12:34:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8179774</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>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8180122</link><pubDate>Thu, 13 Mar 2008 14:57:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8180122</guid><dc:creator>wisemx</dc:creator><description>&lt;p&gt;Very good.&lt;/p&gt;
&lt;p&gt;Is there a chart yet of the restrictions in Linq for C# 3.0 and VB.NET 9 in 3.5?&lt;/p&gt;
</description></item><item><title>New and Notable 226</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8180528</link><pubDate>Thu, 13 Mar 2008 16:33:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8180528</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>Framework Design Guidelines: LINQ</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8181280</link><pubDate>Thu, 13 Mar 2008 18:34:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8181280</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;Wow, it feels like old times ...&amp;amp;#160; I am happy that we are posting a new proposal for additions to&lt;/p&gt;
</description></item><item><title>Upcoming C# 3 Guidance From Microsoft</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8181613</link><pubDate>Thu, 13 Mar 2008 19:16:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8181613</guid><dc:creator>Peter Ritchie's MVP Blog</dc:creator><description>&lt;p&gt;Mircea Trofin has some design guidelines with regard to some C# 3 language additions (that I assume will&lt;/p&gt;
</description></item><item><title>LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8182281</link><pubDate>Thu, 13 Mar 2008 20:21:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8182281</guid><dc:creator>PuntoRete</dc:creator><description>&lt;p&gt;LINQ Framework Design Guidelines&lt;/p&gt;
</description></item><item><title>This is one of the web's most interesting stories on Thu 13th Mar 2008</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8182907</link><pubDate>Thu, 13 Mar 2008 21:04:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8182907</guid><dc:creator>purrl.net |** urls that purr **|</dc:creator><description>&lt;p&gt;These are the web's most talked about URLs on Thu 13th Mar 2008. The current winner is ..&lt;/p&gt;
</description></item><item><title>[LINQ] Les bonnes pratiques à appliquer lors de l'utilisation de LINQ</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8183077</link><pubDate>Thu, 13 Mar 2008 21:14:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8183077</guid><dc:creator>Thomas Lebrun</dc:creator><description>&lt;p&gt;Microsoft vient de mettre &amp;#224; disposition, via le blog de Mircea Trofin , un ensemble de &amp;quot; Design Guidelines&lt;/p&gt;
</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8192095</link><pubDate>Fri, 14 Mar 2008 04:23:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8192095</guid><dc:creator>Mark Kamoski</dc:creator><description>&lt;p&gt;This is great. I really appreciate it. It is just the kind of thing that I have been looking for lately. Since you know a lot about this, as a follow-up, if at all possible, please read my seminal post &amp;quot;Linq-To-Sql and application architectures, design implementations, application layering, physical separation of tier information, etc.&amp;quot; at this link &lt;a rel="nofollow" target="_new" href="http://forums.asp.net/t/1222029.aspx"&gt;http://forums.asp.net/t/1222029.aspx&lt;/a&gt; and provide some assistance. Thank you very much. -- Mark Kamoski&lt;/p&gt;</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8193359</link><pubDate>Fri, 14 Mar 2008 05:58:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8193359</guid><dc:creator>David Nelson</dc:creator><description>&lt;p&gt;The example for the rule &amp;quot;when object model considerations would dictate taking a dependency on some assembly, but taking such a dependency would break dependency management rules&amp;quot; is far too complicated. I have experience in the telecom industry and I can barely understand it.&lt;/p&gt;</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8198448</link><pubDate>Fri, 14 Mar 2008 11:29:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8198448</guid><dc:creator>mohamad</dc:creator><description>&lt;p&gt;Thanks very much for this nice article on LINQ&lt;/p&gt;
&lt;p&gt;wish you good luck&lt;/p&gt;</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8200516</link><pubDate>Fri, 14 Mar 2008 13:25:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8200516</guid><dc:creator>Artiom Chilaru</dc:creator><description>&lt;p&gt;Heya.. a nice article, with some useful data, especially when just starting to learn LINQ.. Thanks )&lt;/p&gt;
&lt;p&gt;P.S. Just wondering.. are you from Romania? )&lt;/p&gt;</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8353110</link><pubDate>Thu, 03 Apr 2008 08:39:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8353110</guid><dc:creator>Sri</dc:creator><description>&lt;p&gt;excellent article, thanks for the effort&lt;/p&gt;</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8353518</link><pubDate>Thu, 03 Apr 2008 14:43:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8353518</guid><dc:creator>Koistya `Navin</dc:creator><description>&lt;p&gt;Very nice hints collection on LINQ! Thanks&lt;/p&gt;</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8424438</link><pubDate>Fri, 25 Apr 2008 20:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8424438</guid><dc:creator>Steve</dc:creator><description>&lt;p&gt;Would like to print this post for reference but IE appears to have problems after the first page. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Any suggestions?&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;</description></item><item><title>re: LINQ Framework Design Guidelines</title><link>http://blogs.msdn.com/mirceat/archive/2008/03/13/linq-framework-design-guidelines.aspx#8435236</link><pubDate>Mon, 28 Apr 2008 15:25:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8435236</guid><dc:creator>mirceat</dc:creator><description>&lt;p&gt;Steve: try copying the article into word, then printing from there. Let me know if that works!&lt;/p&gt;
</description></item></channel></rss>