Actually, I think people are confusing the microsoft.visualbasic namespace with the microsoft.visualbasic.compatibility namespace. The microsoft.visualbasic namespace provides some VSA functions - basically to provide functions to make things easier - kinda like a VFPTools approach. <g>

The truth is, every object oriented framework needs lower level and higher level constructs. Not using them is like saying you won't use your own UDFs in VFP just because they're not part of the language.

yag

>Hi Terry,
>
>>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?
>
>I agree with you that it is not OOP. Do you think C# is? What about "unsafe code" and "go" commands. What about java? It offers include "mylib.*"? Do you think VFP is? <g> All of these above languages *SUPPORT* OOP. In case of VB .NET, MS wanted the VB6 developers to use VB .NET, and including this library solved the problem.
>
>>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?
>
>Yes.
>
>
>>Is the VB .NET language a namespace in the framework or something to be considered quite separate?
>>
>
>The functions in this namespace are static methods of the "VisualBasic" class defined in the "Microsoft" namespace.
>
>>I've already heard the suggestion to switch to C# thanks...<s>
>
>Personally I do not think that this matters. Unlike languages like VFP or VB6, the learning curve here is not to learn the language but the .NET Framework. If you are comfortable with C# go with C#
>
>Kamal