UWP ContentDialog
The ContentDialog class represents a dialog box that can be customized
to contain checkboxes, hyperlinks, buttons, and any other XAML content. The
ContentDialog() constructor initializes a new instance of the ContentDialog
class.
The following UWP app development tutorial creates a simple content dialog where we put a title, a message, and a primary button. Then we displayed the content dialog by calling the ContentDialog class ShowAsync() method. When users click the primary button then the content dialog hides from the app screen.
The UWP app developers generally used a content dialog to request input from the app user or to show information in a modal dialog. The developers can add a ContentDialog to the app page using code or XAML, even they can create a custom dialog class that's derived from ContentDialog.
The ContentDialog class Title property is used to put a title on the content dialog. But the UWP developers can use TitleTemplate to add a complex title element for their app.
The ContentDialog has three built-in buttons. Those are the close button, primary button, and secondary button. In this tutorial code, we only displayed the primary button on the app interface. The ContentDialog class’s PrimaryButtonText property gets or sets the text to display on the primary button.
The ContentDialog class’s ShowAsync() method begins an asynchronous operation to show the dialog. So finally, we can initialize a ContentDialog instance by using ContentDialog() constructor and display it on the app user interface by calling the ShowAsync() method.
The following UWP app development tutorial creates a simple content dialog where we put a title, a message, and a primary button. Then we displayed the content dialog by calling the ContentDialog class ShowAsync() method. When users click the primary button then the content dialog hides from the app screen.
The UWP app developers generally used a content dialog to request input from the app user or to show information in a modal dialog. The developers can add a ContentDialog to the app page using code or XAML, even they can create a custom dialog class that's derived from ContentDialog.
The ContentDialog class Title property is used to put a title on the content dialog. But the UWP developers can use TitleTemplate to add a complex title element for their app.
The ContentDialog has three built-in buttons. Those are the close button, primary button, and secondary button. In this tutorial code, we only displayed the primary button on the app interface. The ContentDialog class’s PrimaryButtonText property gets or sets the text to display on the primary button.
The ContentDialog class’s ShowAsync() method begins an asynchronous operation to show the dialog. So finally, we can initialize a ContentDialog instance by using ContentDialog() constructor and display it on the app user interface by calling the ShowAsync() method.
MainPage.xaml
<Page
x:Class="UniversalAppTutorials.MainPage"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:UniversalAppTutorials"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
mc:Ignorable="d">
<StackPanel
x:Name="stack_panel1"
Margin="50"
Orientation="Vertical"
Background="Pink"
Padding="35"
>
<Button
x:Name="button1"
Content="Show Content Dialog"
Click="Button1_Click"
/>
</StackPanel>
</Page>
MainPage.xaml.cs
using Windows.UI.Xaml;
using Windows.UI.Xaml.Controls;
namespace UniversalAppTutorials
{
public sealed partial class MainPage : Page
{
public MainPage()
{
this.InitializeComponent();
}
private void Button1_Click(object sender, RoutedEventArgs e) {
// Show the content dialog
DiaplyContentDialog();
}
// Custom method to create and diaplay a content dialog
private void DiaplyContentDialog() {
ContentDialog dialog = new ContentDialog() {
Title = "Content Dialog Title",
Content = "This is the content of dialog.",
PrimaryButtonText = "Ok"
};
// Finally, show the dialog
dialog.ShowAsync();
}
}
}
