title: Visual Basic Module v Singleton
body: <p>So I've been programming in C# for the last 6 years or so and now I'm getting my feet wet with VB.net.</p>
  
  <p>The code base I'm working with uses some modules.  To me the module looks a lot like a singleton.  Only one exists; it can be called anywhere inside the namespace.</p>
  
  <p>Is there something I'm missing here? Does VB not support the normal way a singleton is structured (private constructor/public instance field)?</p>