Microsoft.VisualBasic vs System

[jmcilhinney]

I'd suggest that anyone who has ever advocated the non-use of anything from the Microsoft.VisualBasic namespace reads this article. Personally, I found it rather enlightening. There is still the issue of future support for VB6-style methods from the Microsoft.VisualBasic namespace but, from what that article says, that is the ONLY issue. And there is no specific indication that that will ever be an issue anyway. I've now pretty much weaned myself off Microsoft.VisualBasic, so I will still use a System based method if there is one available, but I will not hesitate to use Microsoft.VisualBasic in future if it seems appropriate. Nor will I berate anyone else for doing so.

Edit:
I guess the other issue may be lack of code portability to other .NET languages. I don't think that that is foremost in your average VB developers mind, though. For those who do want as much code portability as possible, stick to System, and don't ever let me see you use "?:" in C#.