http://blogs.msdn.com/vbfaq/archive/tags/Visual+Basic+2005+_2800_Whidbey_2900_/default.aspxTags: Visual Basic 2005 (Whidbey)en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/vbfaq/archive/2004/04/20/116581.aspxTue, 20 Apr 2004 07:23:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:116581vbfaq3http://blogs.msdn.com/vbfaq/comments/116581.aspxhttp://blogs.msdn.com/vbfaq/commentrss.aspx?PostID=116581<P>Posted by: <A href="http://www.philweber.com/">Phil Weber</A>, VB <A href="http://mvp.support.microsoft.com/default.aspx?scid=fh;EN-US;mvpintro">MVP</A><BR /><EM>This post applies to Visual Basic .NET 2002/2003/2005</EM></P> <P><A href="http://www.aliparvaresh.com/">Ali Parvaresh</A> asks: <BLOCKQUOTE> How can I document VB.NET source codes like what you do for C#? </BLOCKQUOTE> </P> <P>This is another feature scheduled for Visual Basic .NET 2005 (ref <A href="http://panopticoncentral.net/archive/2003/11/08/239.aspx">http://panopticoncentral.net/archive/2003/11/08/239.aspx</A>). In the meantime, however, there are a number of <A href="http://www.google.com/search?q=vb.net+xml+documentation">third-party tools</A> which add this capability to VB.NET 2002/2003. One popular (and free) alternative is the <A href="http://www.gotdotnet.com/Community/Workspaces/viewUploads.aspx?id=112b5449-f702-46e2-87fa-86bdf39a17dd">VBCommenter PowerToy</A>.</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=116581" width="1" height="1">GeneralVisual Basic 2005 (Whidbey)http://blogs.msdn.com/vbfaq/archive/2004/04/19/116561.aspxTue, 20 Apr 2004 06:54:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:116561vbfaq3http://blogs.msdn.com/vbfaq/comments/116561.aspxhttp://blogs.msdn.com/vbfaq/commentrss.aspx?PostID=116561<P>Posted by: <A href="http://www.philweber.com/">Phil Weber</A>, VB <A href="http://mvp.support.microsoft.com/default.aspx?scid=fh;EN-US;mvpintro">MVP</A><BR><EM>This post applies to Visual Basic .NET 2005 (&#8220;Whidbey&#8221;)</EM></P> <P><A href="http://altinoren.com/">Gokhan Altinoren</A> asks: <BLOCKQUOTE><EM>What was the design decision behind the fact that VB.NET does not support operator overloading? Will this feature be in the VB.NET specification in the future?</EM> </BLOCKQUOTE> <P></P> <P>Sadly, the VB team failed to consult me while they were designing the language, so I can't comment on why they decided not to support operator overloading in VB.NET (although if I had to guess, I'd wager that it was on the list of &#8220;nice-to-have&#8221; features that had to be postponed in order to ship VB.NET during the Bush administration).</P> <P>The good news is that it is slated for the next release of VB (Visual Basic .NET 2005, code-named <EM>Whidbey).</EM> For more information, see: <BLOCKQUOTE><A href="http://blogs.gotdotnet.com/cambecc/permalink.aspx/5de5a161-9150-4237-a751-127195cceeab">http://blogs.gotdotnet.com/cambecc/permalink.aspx/5de5a161-9150-4237-a751-127195cceeab</A><BR><A href="http://weblogs.asp.net/cfranklin/archive/2003/11/14/37580.aspx">http://weblogs.asp.net/cfranklin/archive/2003/11/14/37580.aspx</A> </BLOCKQUOTE> </P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=116561" width="1" height="1">LanguageVisual Basic 2005 (Whidbey)