private async void BuildPaneAsync(AccountsSettingsPane s, For Microsoft Accounts and Azure Active Directory, it's "".
The URL for the provider varies based on the provider and can be found in the provider's documentation. Next, get a provider using the WebAuthenticationCoreManager.FindAccountProviderAsync method.
private async void BuildPaneAsync(AccountsSettingsPane s,ĪccountsSettingsPaneCommandsRequestedEventArgs e) This tells the system to delay showing the AccountsSettingsPane until we're finished building it. This is where we'll put the code to customize the commands shown in the pane. The BuildPaneAsync method is called whenever the AccountsSettingsPane is shown. This way, your customized pane is only in memory when there's a high chance a user is going to ask for it (because they're on a "settings" or "login" page, for example). Users don't interact with accounts very often, so registering and deregistering your event handler in this fashion helps prevent memory leaks. Protected override void OnNavigatedFrom(NavigationEventArgs e)ĪccountsSettingsPane.GetForCurrentView().AccountCommandsRequested -= BuildPaneAsync In your code behind, override the OnNavigatedTo and OnNavigatedFrom events and add the following code to them: protected override void OnNavigatedTo(NavigationEventArgs e)ĪccountsSettingsPane.GetForCurrentView().AccountCommandsRequested += BuildPaneAsync This tells the system to run our build logic when the user asks to see the pane (for example, clicks our XAML button). To add commands to the pane, we start by registering for the AccountCommandsRequested event handler. Optionally, you can use ShowAddAccountAsync instead of Show, which will return an IAsyncAction, to query for the status of the operation. The pane is empty because the system only provides a UI shell - it's up to the developer to programatically populate the pane with the identity providers. If you run your app and click the "Log in" button, it should display an empty window. You can show it like this: private void LoginButton_Click(object sender, RoutedEventArgs e) The system provides a built-in user interface for managing identity providers and web accounts called AccountsSettingsPane. Lastly, add the following namespaces so you don't have to worry about any reference issues later: using System Īnd an event handler attached to your button in the code-behind: private void LoginButton_Click(object sender, RoutedEventArgs e) Third, create a very basic UI consisting of a simple XAML button and two text boxes. To do this, right click your project, choose Store/Publish > Associate app with the store, and follow the wizard's instructions. Second, in order to connect to identity providers, you'll need to associate your app with the Store. Get set upįirst, create a new, blank app in Visual Studio. For a complete code sample, see the WebAccountManagement sample on GitHub.
0 kommentar(er)
