You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have a prototype for roaming settings via extensions on the Graph user, as well as saving to files in OneDrive. We need a way to consume these from a single standpoint.
Something like:
var settings = new RoamingSettings(DataStore.OneDrive); // DataStore.UserExtensions
I like this setup because it includes consideration for scaling to other data storage types (KVP, Json file, etc.). It also gives us a graceful way to replace the existing RoamingObjectStorageHelper in WCT. I don't see option 1 being easy to build a system with.
Other info
I'd like to move these files to a separate package once PR #76 is merged in.
The text was updated successfully, but these errors were encountered:
Hello shweaver-MSFT, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
Describe the problem this feature would solve
RoamingSettings have been deprecated by the platform but developers still need a way to save settings data that will roam with the user.
https://docs.microsoft.com/en-us/windows/deployment/planning/windows-10-deprecated-features
Describe the solution
We already have a prototype for roaming settings via extensions on the Graph user, as well as saving to files in OneDrive. We need a way to consume these from a single standpoint.
Something like:
I chose to extend IObjectStorageHelper from WCT and replace the existing RoamingObjectStorageHelper
I like this setup because it includes consideration for scaling to other data storage types (KVP, Json file, etc.). It also gives us a graceful way to replace the existing RoamingObjectStorageHelper in WCT. I don't see option 1 being easy to build a system with.
Other info
I'd like to move these files to a separate package once PR #76 is merged in.
The text was updated successfully, but these errors were encountered: