Skip to content

Add missed code style options to automation object#16512

Merged
jmarolf merged 1 commit intodotnet:post-dev15from
jmarolf:bugfix/persist-codestyle-options
Feb 3, 2017
Merged

Add missed code style options to automation object#16512
jmarolf merged 1 commit intodotnet:post-dev15from
jmarolf:bugfix/persist-codestyle-options

Conversation

@jmarolf
Copy link
Copy Markdown
Contributor

@jmarolf jmarolf commented Jan 14, 2017

Customer scenario

Customer is unable to import or export most codestyle settings

Bugs this fixes:

#14810

Workarounds, if any

Manually reset the options on each machine, or log in and have them roam with other VS settings

Risk

Low, we are adding options to the automation object. This fix is very self-contained

Performance impact

Low, export/import of settings is an explicit user actions that has its own dialog and must be initiated by the user, it is not part of any mainline scenario

Is this a regression from a previous update?

Users have always been able to import/export all of tools->options so this is an experience regression, though these options are new so you could say these options have not been shipped before so this is not a regression.

Root cause analysis:

The Automation object class is what is reflected over by VS to import/export settings. As more codestyle settings were added this release we forgot to update the automation object.

How was the bug found?

reported by customer

@Pilchie Pilchie added this to the 2.0 (RTM) milestone Jan 18, 2017
Copy link
Copy Markdown
Member

@Pilchie Pilchie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍, but a couple of questions:

  1. What can we do to prevent this in the future
  2. Do we have a separate bug about updating the baseline profiles so that reset-all-settings works?

@jmarolf
Copy link
Copy Markdown
Contributor Author

jmarolf commented Jan 18, 2017

@Pilchie
1: would require us to re-architect how settings work in roslyn so there are not three places. Should we file a bug around this?
2: filed issue #16599

@Pilchie
Copy link
Copy Markdown
Member

Pilchie commented Jan 20, 2017

Tagging @MattGertz does this meet the bar at this point?

@MattGertz
Copy link
Copy Markdown
Contributor

I'm afraid not. Please move to 2.1, and make sure we have documentation around this.

@jmarolf jmarolf modified the milestones: 2.1, 2.0 (RTM) Jan 20, 2017
@jmarolf jmarolf changed the base branch from master to post-dev15 January 23, 2017 02:44
@jmarolf jmarolf force-pushed the bugfix/persist-codestyle-options branch from 4a591f2 to 0f3002a Compare January 30, 2017 22:15
@jmarolf
Copy link
Copy Markdown
Contributor Author

jmarolf commented Jan 30, 2017

@dotnet/roslyn-ide please review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants