DarranRowe
DarranRowe
I don't think you can, you only really take a dependency on the main runtime. But the Windows App SDK does have the Microsoft.Windows.ApplicationModel.WindowsAppRuntime namespace which houses the deployment manager...
The editor doesn't expose this. The instructions that the official Microsoft documentation gives involves editing the XML directly. You can find this documentation [here](https://docs.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/app-notifications/app-notifications-quickstart?tabs=cs).
Do you have the in app toolbar enabled?  If you do, try disabling it.  There is a known issue where the in app toolbar...
You should just be able to click the same button as you used to disable it.
>or where should I report a bug for errors affecting Windows.Networking.Proximity? As Janine Zhang mentioned in the Q&A post and I actually mentioned in the post you originally posted on...
>I think this repository is the right place If you look around, then you will find that this is part of the footer for this template. It is even present...
>Could you give us a more detailed explanation on those two reasons? It's not about UWP supporting WinAppSDK or not, It's about the Proximity Device as part of the WinRT-API...
Just to make something clear, the Windows App Runtime is strongly versioned to the minor version too. So if you built the application with the Windows App SDK version 1.4,...
With regards to this proposal, what kind of functionality do you believe that it should have relative to the desktop API? As an example, ProcessLauncher has two overloads for RunToCompletionAsync....
This seems to work without issue on Win11. 