Q: Microsoft.VisualBasic Namespace

[Guest]

Hi group,

I've seen a number of articles where .NET programmers argue against using
the Microsoft.VisualBasic namesapce; I've also seen others that promote the
use of this namespace.

What is a general consensus on the use of the namespace by the people who
frequent this board?

And if the consensus is to NOT use the Microsoft.VisualBasic namespace, then
what is the alternative for creating a COM class? When I create a new Com
Class item, NET automatically puts the following attribute at the top of the
object:
<ComClass(PrototypeObjects.ClassId, PrototypeObjects.InterfaceId,
PrototypeObjects.EventsId)>

Thanks for your input.

 

[schneider]

Use it if you need it. If I remember correctly, a lot of the functionality
of the library is optimized well.
I think most who are against its use are anti VB coders.

Schneider