title: Are using modules in VB.NET considered bad practice?
body: <p>During the design of a new application I was wondering if using a module with properties is considered to be a bad practice. </p>
  
  <p>Some example code:</p>
  
  <pre><code>Module modSettings
  
     public property Setting1 as string
  
     public property DatabaseObject as IDatabaseObject
  
  End Module
  </code></pre>
  
  <p>The code above is just an example to emphasize my question. In the past, this structure was used a lot in VB6. In the past I used it as well in my .NET projects. </p>
  
  <p>But nowadays with buzzwords like Dependency Injection, Testability and Separation of Concerns the above structure smells bad. I can't really describe why, but it just feels wrong. I must admit I'm not very familiar with the keywords above, yet.</p>
  
  <p>So I'm wondering whether the above code really <strong>is</strong> a bad practice. If so, what would you use a <code>Module</code> for?</p>