Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate options stored in local registry to roaming options, where it makes sense #62748

Open
3 tasks
Tracked by #58717 ...
tmat opened this issue Jul 18, 2022 · 1 comment
Open
3 tasks
Tracked by #58717 ...

Comments

@tmat
Copy link
Member

tmat commented Jul 18, 2022

Audio all options backed by LocalUserRegistryOptionPersister storage and decide which ones should roam and which should stay local (the later would be mostly those that are not settable in UI by customers).

  • Internal options used just for internal debugging can be migrated directly to LocalClientSettingsStorageLocation, without fallback to old storage
  • Customer visible options (for which we have UI) should be migrated to RoamingProfileStorageLocation (which uses ISettingsManager) with read fallback to legacy local registry reading code path (setting the option would always use ISettignsManager API).
  • Options used by customers to work around issues that do not have UI should be revisited. We should consider if the workaround is still relevant (and possibly remove the option), or treat it as other customer visible options.
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Jul 18, 2022
@tmat
Copy link
Member Author

tmat commented Jul 18, 2022

@jasonmalinowski FYI

@tmat tmat added this to the Backlog milestone Jul 18, 2022
@vatsalyaagrawal vatsalyaagrawal added Concept-Continuous Improvement and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants