<?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>Extension methods in C# 3.0</title><link>http://blogs.msdn.com/pedram/archive/2007/06/02/extension-methods-in-c-3-0.aspx</link><description>You can think of extension methods as the ability to add instance methods to already existing types. Having said that, I would immediately also tell you that it is just an illusion. You are not actually adding a method to an existing type. It is just</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Is C# becoming a functional language?</title><link>http://blogs.msdn.com/pedram/archive/2007/06/02/extension-methods-in-c-3-0.aspx#3048816</link><pubDate>Sat, 02 Jun 2007 21:27:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3048816</guid><dc:creator>David's blog</dc:creator><description /></item><item><title>re: Extension methods in C# 3.0</title><link>http://blogs.msdn.com/pedram/archive/2007/06/02/extension-methods-in-c-3-0.aspx#7041138</link><pubDate>Wed, 09 Jan 2008 17:52:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7041138</guid><dc:creator>JH</dc:creator><description>&lt;p&gt;Pedram,&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; I am experiencing the same issue (The listing returns null for mi). Have you been able to determine how intellisense is able to discover the extension method?&lt;/p&gt;</description></item><item><title>re: Extension methods in C# 3.0</title><link>http://blogs.msdn.com/pedram/archive/2007/06/02/extension-methods-in-c-3-0.aspx#7041263</link><pubDate>Wed, 09 Jan 2008 17:59:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7041263</guid><dc:creator>pedramr</dc:creator><description>&lt;p&gt;JH, IntelliSense certainly does not use reflection in here. Let’s remember, Extension methods are a compile-time trick played by the compiler. They are effectively nothing more than a static method. Reflection can only expose methods which are real methods exposed by your type.&lt;/p&gt;
</description></item><item><title>re: Extension methods in C# 3.0</title><link>http://blogs.msdn.com/pedram/archive/2007/06/02/extension-methods-in-c-3-0.aspx#7044250</link><pubDate>Wed, 09 Jan 2008 21:54:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7044250</guid><dc:creator>JH</dc:creator><description>&lt;p&gt;Yeahp... I knew it couldn't be using reflection... I'm wondering what mechanism it's using to discover the extension methods.&lt;/p&gt;</description></item><item><title>re: Extension methods in C# 3.0</title><link>http://blogs.msdn.com/pedram/archive/2007/06/02/extension-methods-in-c-3-0.aspx#7053402</link><pubDate>Thu, 10 Jan 2008 13:08:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7053402</guid><dc:creator>pedramr</dc:creator><description>&lt;p&gt;JH, the IntelliSense cannot rely only on the metadata included in a compiled assembly because in many cases you need IntelliSense on the code which does not even compile. I don’t know the mechanisms used by the C# IntelliSense to achieve this but I would suspect that it uses the parsing capabilities of the C# parser to build a code tree.&lt;/p&gt;
</description></item></channel></rss>