<?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>Debugging Features in C# 3.0 Part 1</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx</link><description>Overview C# 3.0 introduces many new constructs and opens entirely new ways of thinking and developing code. In this article I will talk about the new debugging features that make it easy to see the running code and better understand it. In my experience</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Debugging C# 3.0 Part1</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx#2977548</link><pubDate>Wed, 30 May 2007 03:16:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2977548</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>re: Debugging Features in C# 3.0 Part 1</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx#2983029</link><pubDate>Wed, 30 May 2007 10:22:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2983029</guid><dc:creator>Matthieu MEZIL</dc:creator><description>&lt;p&gt;Good job! :-)&lt;/p&gt;
&lt;p&gt;As I said in my blog yesterday (&lt;a rel="nofollow" target="_new" href="http://blog.developpez.com/index.php?blog=121&amp;amp;title=extension_methods_et_intellisence_1&amp;amp;more=1&amp;amp;c=1&amp;amp;tb=1&amp;amp;pb=1"&gt;http://blog.developpez.com/index.php?blog=121&amp;amp;title=extension_methods_et_intellisence_1&amp;amp;more=1&amp;amp;c=1&amp;amp;tb=1&amp;amp;pb=1&lt;/a&gt;), in Watch, Execute Window or breakpoint condition, extension methods are not proposed by intellisence :-(&lt;/p&gt;
&lt;p&gt;Perhaps in Orcas Beta 2 ;-)&lt;/p&gt;
</description></item><item><title>Infinite sequences</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx#2987089</link><pubDate>Wed, 30 May 2007 14:30:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2987089</guid><dc:creator>onovotny</dc:creator><description>&lt;p&gt;Does the debugger take into account that not all enumerators have a set number or results, or that the results might be quite large? &amp;nbsp;You might have an enumerable that returns an unending sequence of something. &amp;nbsp;The debugger should be able to handle the &amp;quot;accidental&amp;quot; selection of the results view w/o freezing the IDE.&lt;/p&gt;
</description></item><item><title>re: Debugging Features in C# 3.0 Part 1</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx#2989651</link><pubDate>Wed, 30 May 2007 18:54:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2989651</guid><dc:creator>Sree_c</dc:creator><description>&lt;p&gt;Thanks Matthieu and yes there will be intellisence in the watch and the immediate window for extension methods and in fact i will update the article to mention/show it. &lt;/p&gt;
&lt;p&gt;I understand Onovotny, an Enumeration can certainly be infinite and there is no clear way of identifying this. An Infinite Enumeration will behave just like a function that times out when entered in the watch. In fact i will be metioning this in my next article on steeping. The other case to think of is when the enumeration yields zero results, we give an error message for that ,again i will update the article to mention this.&lt;/p&gt;
&lt;p&gt;thanks guys and keep it comming &lt;/p&gt;
</description></item><item><title>re: Debugging Features in C# 3.0 Part 1</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx#2994400</link><pubDate>Thu, 31 May 2007 01:28:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2994400</guid><dc:creator>onovotny</dc:creator><description>&lt;p&gt;Sree,&lt;/p&gt;
&lt;p&gt;Maybe it's too late, but I hope not -- how about an attribute that can go on enumerators (and enumerable methods -- yield return) that's a debugger hint not to eval. &amp;nbsp;Something Like DebuggerNoEnumerateAttribute. &amp;nbsp;&lt;/p&gt;
</description></item><item><title>re: Debugging Features in C# 3.0 Part 1</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx#3031986</link><pubDate>Sat, 02 Jun 2007 02:56:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3031986</guid><dc:creator>Sree_c</dc:creator><description>&lt;p&gt;Ok let me be clear, there is an explicit user interaction required for the Enumeration to be enumerated. There is nothing automatic ... is there some specific reason that this is of consern for you. We can certainly add an attribute if enough user find this intresting. And on stepping the results view alsomatically disabled and is not enabled untell the user explicitly wished to refresh.&lt;/p&gt;
</description></item><item><title>Community Convergence XXVIII</title><link>http://blogs.msdn.com/sreekarc/archive/2007/05/19/debugging-features-in-c-3-0-part-1.aspx#3431401</link><pubDate>Thu, 21 Jun 2007 00:26:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3431401</guid><dc:creator>Charlie Calvert's Community Blog</dc:creator><description>&lt;p&gt;Welcome to the XXVIII Community Convergence. In these posts I try to wrap up events that have occurred&lt;/p&gt;
</description></item></channel></rss>