title: Why are a visual studio project's command-line settings stored per user? Is it OK to check-in (and share) a .user setting file?
body: <p>We're creating an application that understands some command-line parameters.   There are some default's we would like to supply on the command-line when debugging, and these are easily set in the project settings <a href="https://stackoverflow.com/questions/298708/debugging-with-command-line-parameters-in-visual-studio">as explained here</a>.   </p>
  
  <p>The thing is visual studio stores these settings in a *.csproj.<strong>user</strong> file, and the default settings for integrated source control do not check-in *.<strong>user</strong> files.   We would like to just have these default command-line parameters in everyone's IDE when debugging this project.</p>
  
  <p>Often (but not always) when visual studio guides you into doing things a certain way it is for good reason.  We probably don't want to just check-in someone's .csproj.<strong>user</strong> file... right?</p>
  
  <p>This question is has a few parts:</p>
  
  <ul>
  <li>Why does Visual Studio store this
  particular setting per user?  </li>
  <li>Is there a way to alter this behavior?  - Would doing so bring bad juju? </li>
  <li>Under these circumstances is it OK to check-in and share a <strong>.user</strong> file?</li>
  <li>Is there a better way to accomplish what we are
  trying to do here?</li>
  </ul>
  
  <p>Thank you -</p>