diff --git a/README.md b/README.md index f81c7ba..59bda92 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ A Notification Flyout that looks and feels exactly like the native Volume, Netwo [![](http://img.youtube.com/vi/8EoZ4pGWTkY/0.jpg)](http://www.youtube.com/watch?v=8EoZ4pGWTkY "Notification flyout demo") # Getting started # -Some parts of this guide refers to the [Host a custom WinRT XAML control in a WPF app using XAML Islands](https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands) article. If in doubt, refer to the article, or post an issue on this repro. +Many parts of this guide refers to the [Host a custom WinRT XAML control in a WPF app using XAML Islands](https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands) article. If in doubt, refer to the article, or post an issue on this repro. ## Create a UWP project ## 1. In Visual Studio 2019, create a new UWP app project project. Make sure the target version and minimum version are both set to Windows 10, version 1903 (Build 18362) or a later release. @@ -57,8 +57,22 @@ namespace MyUWPApp ## Create a WPF project ## 1. In Visual Studio 2019, create a new WPF App (.NET Core) project. -2. In the WPF app project, install the [Microsoft.Toolkit.Wpf.UI.XamlHost](https://www.nuget.org/packages/Microsoft.Toolkit.Wpf.UI.XamlHost) and [NotificationFlyout.Wpf.UI.Controls](https://www.nuget.org/packages/NotificationFlyout.Wpf.UI.Controls/) NuGet packages (latest stable version). -3. Open the `App.xaml` file and replace the contents of this file with the following XAML. Replace `MyWPFApp` with the namespace of your WPF app project. +2. In Solution Explorer, double-click the WPF project node to open the project file in the editor. +3. Replace the contents of this file with the following xml. +```xml + + + WinExe + netcoreapp3.1 + true + uap10.0.19041 + AnyCPU;x64 + + +``` +4. In Solution Explorer, right-click the Dependencies node under the WPF project and add a reference to your UWP app project. +5. In the WPF app project, install the [Microsoft.Toolkit.Wpf.UI.XamlHost](https://www.nuget.org/packages/Microsoft.Toolkit.Wpf.UI.XamlHost) and [NotificationFlyout.Wpf.UI.Controls](https://www.nuget.org/packages/NotificationFlyout.Wpf.UI.Controls/) NuGet packages (latest stable version). +6. Open the `App.xaml` file and replace the contents of this file with the following XAML. Replace `MyWPFApp` with the namespace of your WPF app project. ```xaml ``` -4. Delete the MainWindow.xaml file from the WPF app project. -5. In your WPF project, right-click the project node, select Add -> New Item, and then select Class. Name the class Program and click Add. -6. Replace the generated `Program` class with the following code and then save the file. Replace `MyUWPApp` with the namespace of your UWP app project, and replace `MyWPFApp` with the namespace of your WPF app project. +7. Delete the MainWindow.xaml file from the WPF app project. +8. In your WPF project, right-click the project node, select Add -> New Item, and then select Class. Name the class Program and click Add. +9. Replace the generated `Program` class with the following code and then save the file. Replace `MyUWPApp` with the namespace of your UWP app project, and replace `MyWPFApp` with the namespace of your WPF app project. ```c# using NotificationFlyout.Wpf.UI.Controls; using System; @@ -94,8 +108,10 @@ namespace MyWPFApp } } ``` -7. Clean the WPF app project and then build it. -8. Run the WPF app. +10. Right-click the project node and choose Properties. +11. On the Application tab of the properties, click the Startup object drop-down and choose the fully qualified name of the `Program` class you added in the previous step. +12. Clean the WPF app project and then build it. +13. Run the WPF app. # Limitations and workarounds # All limitions found in this [article](https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/xaml-islands#limitations-and-workarounds) will affect how you build an app using this control. We have of course have added a work around for when the Windows theme is changed by the user 🎉!