Bruce is right.

Basically VB has been complying more and more to a C++ construct. I think
the problems lies with old dogs like myself who still think in a procedural
format and maybe we might be talking Latin to a Irish man.
Microsoft lost big time to Sun recently and are not allowed to use Java as a
key word so that's why we have C#.
I guess this is fair enough as basically it was the war between netscrap and
exploder that made HTML the bolox it is now.
As I mentioned above about old dogs my new tricks may have to be C# and
VB.net and VBscript depending on the application required.
There is a lot to be said for VBA for the empowerment of business in terms
of customisation rather than hardcore programming. Where it doesn't take a
high brow to provide a bespoke solution.

As a end note with the advent of the web I think this has possibly been the
most rapid period of developmental style that we have ever seen. So
hopefully the dust will settle and my head will stop spinning.
One interesting thing about name spaces is that online xml libraries could
be called and knitted together with xml templates as object model interfaces
making the monolithic .Net will be irrespective of provider.
Scary days if your a fan of Orwell.