Document the liveshare.{account,accountProvider} Settings

[derekclair]

I've been trying to figure out how to configure both the "liveshare.account" & "liveshare.accountProvider" settings. The best I could come up with was that they're expected to be type: string (from the Extensions package.json file...). I would rather have sent a PR than Feedback, but that's the best I could do. Could you offer any clarification on those two settings?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 6a671ef3-7321-b9b6-2ca5-9378c613a31b
• Version Independent ID: 26462292-c010-d177-6ebb-6d63ae82e5f7
• Content: Collaborate using Visual Studio Code - Visual Studio Live Share - Visual Studio Live Share
• Content Source: docs/use/vscode.md
• Service: vs-liveshare
• Product: visual-studio-family
• GitHub Login: @Chuxel
• Microsoft Alias: clantz

[daytonellwanger]

I think these settings are probably deprecated.
@jasongin to provide more information.

[jasongin]

They are not deprecated, but they are rarely needed. They enable you to select which account should be used for automatic sign-in in case you have cached credentials for multiple accounts available.

For example, imagine you work on 2 projects with which you want to sign in with different identities. You could set the "liveshare.account" setting to different email addresses in each project directory to ensure they each automatically sign-in with the correct account. The "liveshare.accountProvider" setting could be set to either "microsoft" or "github" in case you use the same email address with multiple providers.

[Luckz]

Can the signed-in account itself be remembered across sessions? When do 'cached credentials' expire? This seems a little unclear.

[LongLiveCHIEF]

They are not deprecated

Is this still the case?

I want to get rid of the pop-up prompt to choose either microsoft or github each time i start a session, and it also makes it easier to share docs with teamates on the settings that make it work within our network. Sharing a small json snippet and then it just works is much easier than telling/documenting "look for popup, choose selection, " ...