title: Best Practice for storing settings for a .NET Windows Service: Service Property Settings, Serialization,
body: <p>I am working on a .NET Windows Service where I am trying to store settings that will be used when the service is started and while it is running.  I have searched through posts on SO and found that using the Settings in the properties of the project is great for use with console and winforms applications.  However, Google and SO are silent when it pertains to storing these settings with a windows service.</p>
  
  <p>Does anyone one know if it is proper to use these settings in a .NET service?  If not, is Serialization my next best choice?  Has anyone had practical uses for settings in a service and found that it is best to use a specific method?</p>