2

Closed

Solution Settings File

description

When a solution is opened, look for a .vssettings file of the same name next to the .sln file. If it exists, load those settings. This would allow devs to check in .vssettings files to source control along with their solution and have it automatically applied. Useful for open source projects.

Consider security. I'm not sure whether .vssettings files could be harmful any more than loading a foreign solution, but perhaps it would be best to disable this feature by default.

Consider ignoring the associated settings file with the solution (saved in the .suo) or perhaps make this behavior optional and allow users to choose which has precedence.
Closed May 13 at 1:40 PM by davedev

comments

dcazzulino wrote Aug 26, 2013 at 3:55 AM

but perhaps it would be best to disable this feature by default
It should be ON by default. Otherwise, nobody would ever find about it. It should "just work" by default.

wrote May 13 at 1:40 PM

Resolved with changeset 74397: - Added a feature for creating/exporting and automatically importing a solution's settings file ([solution_name].vssettings) in the same directory as the current .sln file.
  • Fixed a bug that caused the toolbar to disappear when switching settings.
  • Fixed a feature introduced by the previous changeset that failed to import the original settings when selected.
  • Some small additions to classes in preparation for future refactoring.
  • Changed the package title and the primary command bar caption into constants to avoid duplication.
  • Fixed most code analysis warnings.