Why are a visual studio project's command-line settings stored per user? Is it OK to check-in (and

Posted by DanO on Stack Overflow See other posts from Stack Overflow or by DanO
Published on 2009-09-01T16:53:03Z Indexed on 2010/05/20 16:20 UTC
Read the original article Hit count: 218

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 as explained here.

The thing is visual studio stores these settings in a *.csproj.user file, and the default settings for integrated source control do not check-in *.user files. We would like to just have these default command-line parameters in everyone's IDE when debugging this project.

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.user file... right?

This question is has a few parts:

  • Why does Visual Studio store this particular setting per user?
  • Is there a way to alter this behavior? - Would doing so bring bad juju?
  • Under these circumstances is it OK to check-in and share a .user file?
  • Is there a better way to accomplish what we are trying to do here?

Thank you -

© Stack Overflow or respective owner

Related posts about visual-studio

Related posts about command-line