title: Global vs Singleton in .NET
body: <p>I have a very common situation here. And for years I haven't found if what i am doing is RIGHT by industry standards.Consider an application which connects to the database, but where the connection string instead of being stored in some file/setting is being passed as a command line parameter at startup OR the database is browsed to at the time the application starts up.</p>
  
  <p>Well it becomes necessary to save that connection string somewhere within the scope of the app. Most common way I have seen it done is a module or global class with get/set methods to save the connections string. Another way I would do it is using Singleton. 
  Either options my DAL can access the connection string when it needs to through a GetConnectionString method.</p>
  
  <p>Is there a BETTER way of doing this?</p>
  
  <p><strong>Update:</strong> i do not have a config file and even if I did I would need the connection string to be read once for the life of the application instance. can you elaborate on the "inject it into any classes" part</p>