<?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>MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx</link><description>Visual C# Whidbey really does rock, don't believe me? I'll show you in this MSDN TV episode . Things I showed: Language/Framework Features Generics Anonymous Methods DataSet XML serialization File class enhancements IDE Features Code Expansions/Snippets</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#77566</link><pubDate>Sat, 21 Feb 2004 12:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:77566</guid><dc:creator>senkwe</dc:creator><description>Just watched it, great show! And thanks for setting your IDE to a big, bold font for good code visibility.</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#77689</link><pubDate>Sat, 21 Feb 2004 22:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:77689</guid><dc:creator>Dan Fernandez</dc:creator><description>Thanks, definitely appreciate it :)&lt;br&gt;&lt;br&gt; I've noticed that a lot of people think that Lucida Console is *the* demo font, but my personal opinion and experience is that Arial Black is much better.  As you correctly pointed out, the thicker a font, the easier it is to read at a long distance (the letters don't blend together).  The only issue is with Arial Black is that it isn't a fixed width font, but for demo purposes I thnk its fine.</description></item><item><title>Robert Scoble</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#78668</link><pubDate>Mon, 23 Feb 2004 21:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:78668</guid><dc:creator>TrackBack</dc:creator><description>Robert Scoble</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#79760</link><pubDate>Wed, 25 Feb 2004 11:48:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:79760</guid><dc:creator>Luc Cluitmans</dc:creator><description>Cool features!&lt;br&gt;&lt;br&gt;One thing has me worried though, related to features that add code, such as the 'Encapsulate field' feature. The problem is, how does this interact with personal preferences of coding style? I'm not talking about  variable naming conventions, but about *where* the newly generated code appears.&lt;br&gt;&lt;br&gt;I myself prefer to have a region for all fields (fields are always private in my code) at the bottom of the source file and have property accessors in a different region. Is there a way to configure where newly generated goes (that would be nice for  the GUI designer too)? Or, as a workaround, is there a refactoring that would allow you to move a code fragment (the newly generated property) to another region (selected from a list)? Of course manual copy and paste does the trick, but just right-clicking the property and tell the IDE to move it to the end of the region named 'properties' (selected from a pop-up list) would be nicer.&lt;br&gt;</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#80209</link><pubDate>Thu, 26 Feb 2004 04:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:80209</guid><dc:creator>Dan Fernandez</dc:creator><description>Hi Luc, &lt;br&gt;&lt;br&gt;Thanks for the feedback, definitely appreciated.  I've passed this on to Anson Horton our IDE PM to see if he knows of an easy way to do this, but I think you would have to write a macro to be able to accomplish this.  The Encapsulate field refactoring is a fully customizable xml file (PDC bits location: C:\Program Files\Microsoft Visual Studio .NET Whidbey\VC#\ExStencil) so you could add or change this in whatever way you would like - ex: put the private variable in a new region, but it won't have the ability to choose regions in the editor.&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;-Dan</description></item><item><title>MSDN TV で Whidbey 版 C# 開発環境をプレビュー (ダン フェルナンデス)</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#82429</link><pubDate>Tue, 02 Mar 2004 08:13:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:82429</guid><dc:creator>河端善博の .TEXT でウェブログ</dc:creator><description>MSDN TV ? Whidbey ? C# ?????????? (?? ???????)</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#88580</link><pubDate>Fri, 12 Mar 2004 15:14:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:88580</guid><dc:creator>John Cousins</dc:creator><description>One thing I noticed: when you were creating a constructor for a class in your video, you manually inserted the open/close curly braces, whereas some of the other nice features you were showing did this automatically!  Are you planning to incorporate a feature to facilitate this?</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#88585</link><pubDate>Fri, 12 Mar 2004 15:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:88585</guid><dc:creator>John Cousins</dc:creator><description>In fact, thinking about it, why don't you automatically create a (default empty) constructor when you're using that nice code expansion feature for a class?  It would imo be a very convenient thing to have.</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#88971</link><pubDate>Sat, 13 Mar 2004 07:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:88971</guid><dc:creator>Dan Fernandez</dc:creator><description>Thanks John, I totally agree with you on the open/close curly braces for the constructor (and for all methods), but I'm not sure if having a default empty constructor in the class expansion is the way to go. Would you always want to have an empty constructor for your classes? If so, at worst you could always modify the expansion yourself and add the default constructor, but another option might be to have multiple expansions, one for a class w/ no constructor one for a class with an empty constructor.</description></item><item><title>Refactoring and Intelliarguments</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#89315</link><pubDate>Sun, 14 Mar 2004 14:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:89315</guid><dc:creator>Scott Munro</dc:creator><description>Refactoring and Intelliarguments</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#90691</link><pubDate>Tue, 16 Mar 2004 20:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:90691</guid><dc:creator>parekodi</dc:creator><description>Hi,&lt;br&gt;I am unable to view Refactor option when I right click on the variable.&lt;br&gt;Also I am unable to add property using &amp;quot;property&amp;quot; and tab combination.&lt;br&gt;Should I do any kind of IDE settings before I use these features ?&lt;br&gt;My versions are VS2003 (7.1.3088) and .NetFramework is (1.1.4322)</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#90697</link><pubDate>Tue, 16 Mar 2004 21:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:90697</guid><dc:creator>Dan Fernandez</dc:creator><description>Parekodi - The settings that I showed are not for VS2003 but rather  for the next version of Visual Studio, codenamed &amp;quot;Whidbey&amp;quot;, which is now known Visual Studio 2005.&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;-Dan</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#91799</link><pubDate>Thu, 18 Mar 2004 09:25:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:91799</guid><dc:creator>John Cousins</dc:creator><description>Dan, is there a place in MSDN subscriber downloads where I can download the beta of Whidbey?</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#110664</link><pubDate>Sat, 10 Apr 2004 00:09:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:110664</guid><dc:creator>Evangelos Hadjichristodoulou</dc:creator><description>I've Seen the MSDN TV video. Great. I want to use them now. I have VS Whidbey PDC version. I do not see any refactoring options. Will I need to wait for the beta version or do I need a configuration change in current verion I have?</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#110718</link><pubDate>Sat, 10 Apr 2004 03:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:110718</guid><dc:creator>Dan Fernandez</dc:creator><description>Evangelos,&lt;br&gt;&lt;br&gt;A couple of things, the refactorings I showed are only available in C# and you can't use them in ASP.NET unless the C# files are in a custom directory named &amp;quot;code&amp;quot; (at least in that build).  For test purposes, try creating a windows form project, right-click in the code view and see if the refactoring options are available.&lt;br&gt;&lt;br&gt;Hope this helps,&lt;br&gt;-Dan</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#111134</link><pubDate>Sun, 11 Apr 2004 08:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:111134</guid><dc:creator>Evangelos Hadjichristodoulou</dc:creator><description>Great!!! It works in a Windows app. Losts to play then... What I wouldent give to get involved in this project...&lt;br&gt;&lt;br&gt;Thank Dan.&lt;br&gt;Later</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#121995</link><pubDate>Wed, 28 Apr 2004 13:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:121995</guid><dc:creator>Björn Morén</dc:creator><description>Great features to have. I'm looking forward to next VS.&lt;br&gt;&lt;br&gt;But don't you guys follow your own code writing recommendations?&lt;br&gt;&lt;br&gt;&lt;a target="_new" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/cpconnamingguidelines.asp"&gt;http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/cpconnamingguidelines.asp&lt;/a&gt;&lt;br&gt;&lt;br&gt;Regards,&lt;br&gt;Bj&amp;#246;rn</description></item><item><title>re: MSDN TV on Visual C# "Whidbey"</title><link>http://blogs.msdn.com/danielfe/archive/2004/02/20/77443.aspx#132770</link><pubDate>Sun, 16 May 2004 11:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:132770</guid><dc:creator>nasir jasim</dc:creator><description>I've seen the show.IT WAS AMAZING&lt;br&gt;thank you very much.andI hope if there's more coming demos on C# Whidbey ??&lt;br&gt;</description></item></channel></rss>