Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
More OOP w/o Microsot.VisualBasic?
Message
 
To
15/05/2002 02:50:09
General information
Forum:
ASP.NET
Category:
Other
Miscellaneous
Thread ID:
00656734
Message ID:
00656764
Views:
21
>>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 don't see how it would be more OOP, though I do see how it could lead to confusion if you're sharing source with other developers. If you're not diggin' the VB.NET functions, can't you just not use them?

Hey Mike, long time no see!

Good question. If I drop the namespace: Microsoft.VisualBasic to clean up VB in size and messiness, I drop doevents and a lot of stuff that seems mainly desktop windows form related. Do you know what's in the namespace as far as things that might be required vs compatibility related?

Why did they make it part of the framework instead of putting it in the language? The language of VB .NET is not contained in a framework namespace, right?

I see .NET as a huge Web Connect, but there I knew what was VFP and what was Rick's stuff pretty clearly. In .NET I see incorrect phrases all the time like: The framework has more than 2,000 base classes, when in truth it has one base class (object) as a single rooted hierarchy of classes. Every other class is a sub class of object, and so in that context I'm trying to understand what this one special namespace, Microsoft.VisualBasic is.

I guess I am concerned with purity today as I hear many comments regarding the crudity of VB .NET having all that compatibility baggage onboard, when if it is a framework namespace that can be left out, this would leave VB somewhat clean like C#.

I'm trying to grasp it as many of my clients are asking whether they should move into C# or VB .NET. I'm learning both, but most of my clients will barely be able to get into one. I found Ken Levy's comments helpful, and I've heard the RAD future of VB as a benefit mentioned strongly by many higher ups in the .NET employ of MS. When I hear the list servers on C# it seems like they are really into low level concerns that might tend to drive their languages future away from rad.

How is your study going? Found any good resources? The list servers seem to be my best source so far although I'm enjoying many of the books. About 20 purchased so far. <s>

Good on ya,
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform