title: Use Singleton pattern for error logging class?
body: <p>I currently have a class written in C# which does some simple error logging stuff. It's been used quite extensively throughout my project.</p>
  
  <pre><code>class LogError
  {
      //constructor
      public LogError() { }
  
      //public methods
      public void saveToTextFile() { }
  
      //other similar methods...
  }
  </code></pre>
  
  <p>But, it doesn't seems a good design of this class, as every time I have to create an instance of <code>LogError</code> class before <code>saveToTextFile()</code> method can be used. </p>
  
  <p>So I am thinking of re-designing this class. Would this be a good case to apply Singleton pattern? What about making it static class instead? Any suggestions? Thanks. </p>