Everything John said is sensible - although IMHO there are definitely times
when global variables make sense.
But, as evil as it may be, one can still implement a VB Module, which is
roughly the equivalent of a VB6 "General" or BAS module.
It appears that the way .NET treats these is essentially what John
recommends to do - it creates a static (or Shared in VB) entity - which
looks an awful lot like a class - where all routines are automatically also
Anyone know exactly what a VB Module is ?
Anyway, that is one way to implement global members.