| Reporter |
Hadi Hariri (hadihariri)
|
|---|---|
| Created | Apr 5, 2012 3:05:30 PM |
| Updated | Apr 5, 2012 3:05:30 PM |
| Priority | Normal |
| Type | Bug |
| Fix versions | No Fix versions |
| State | Submitted |
| Assignee | Sergey Coox (coox) |
| Subsystem | No subsystem |
| Affected versions | No Affected versions |
| Fixed in build | No Fixed in build |
If I go and delete my *.sln.DotSettings.user file. When I reopen VS, R# recreates that file with some default settings. Those settings thus override my team settings. Note that I did not change any settings yet.
What that means is for every new team member who clones my repository, I have to tell them to over-write their user settings with my team settings. And if they've done that, every time I make a team setting, they have to override it. Unacceptable. :)
Some options that come to mind:
1. Don't automatically create the .user settings file. Instead, wait till the user actually tries to set a personal setting to create it.
2. When creating a .user settings file, create an empty .user setttings file that inherits all its settings from the one after it (whether it's a team settings or computer one). Ideally do this whether or not you do #1.
3. Change your default settings to be more consistent with VS standards (ok, this is just my personal opinion). I don't understand why the Braces Layout section has some settings as BSD and some as GNU. Why would anyone want to have inconsistent bracing styles as a default?
While I would love the ability to be able to see if a setting is inherited vs overridden in the next release, at minimum I think you need to fix the issue I just described.
What that means is for every new team member who clones my repository, I have to tell them to over-write their user settings with my team settings. And if they've done that, every time I make a team setting, they have to override it. Unacceptable. :)
Some options that come to mind:
1. Don't automatically create the .user settings file. Instead, wait till the user actually tries to set a personal setting to create it.
2. When creating a .user settings file, create an empty .user setttings file that inherits all its settings from the one after it (whether it's a team settings or computer one). Ideally do this whether or not you do #1.
3. Change your default settings to be more consistent with VS standards (ok, this is just my personal opinion). I don't understand why the Braces Layout section has some settings as BSD and some as GNU. Why would anyone want to have inconsistent bracing styles as a default?
While I would love the ability to be able to see if a setting is inherited vs overridden in the next release, at minimum I think you need to fix the issue I just described.