The Microsoft.VisualBasic library and namespace is just as core a part of the framework as the Microsoft.CSharp library and namespace or any of the other framework DLLs. It comes down when you download the .NET framework and is part of the redist.

I understand some people not using the VB.Compatibility namespace, which is used more for VB6 upgraded apps, but this one should be thought of as just another framework piece.

One nice thing about the .NET framework is that it allows the various teams to implement language and feature enhancements. Basically, we are divided into a Framework team, and various language teams. Instead of having to put everything together, we separate things into DLLs. Taking out the VisualBasic namespace would be like saying I never want to use the System.Data namespace.

yag

>I am interested in any comments along the line of whether other VB .NET developers are removing Microsoft.VisualBasic namespace from the default project imports list.
>
>Is it more OOP oriented to do so?
>
>If one wants to be more OOP oriented and disciplined, should one endeavor to find methods of the classes in the framework that are being used rather than use a function or statement from the language?
>
>Is the VB .NET language a namespace in the framework or something to be considered quite separate?
>
>etc, etc.
>
>I've already heard the suggestion to switch to C# thanks...<s>
>
>happy coding everyone,
>TIA