Currently i have a VSTO Outlook addin that is using the default settings provider to manage configurations. All User configs are marked at Local scope and are thus saved under %LocalAppData%. I have a reason to change them to be Roaming (%AppData%) scope and it seems to work on my computer (local profile), but there is some uncertainty that it might not be that way for everyone.
So my concern is, is there any scenario in AD/GP environments or otherwise, if i did swap over from Local to Roaming where the addin would cease to work due to the Roaming folder being inaccessible or something like that?
Been trying to figure out any scenarios like this but really the only things i can find is that:
- administrators may turn off roaming profiles, which would just make the roaming folder act like the local folder? (addin still works locally),
- admins may limit the size of the profile which breaks syncing. (addin still works locally)
- admins may exclude my folder from syncing (addin still works locally)
Basically worst case scenario i've been able to come up with is that configs will be local to the device, which is exactly how it works now, no problem. For those that do use roaming profiles, if i cause them exceed their quota would that possibly break the whole profile?
What else could possibly go wrong? Which pitfalls am i missing (and what are the best practices to overcome them (c# bonus))?
