[Feature] CommunityToolkit.AppServices package #301
Sergio0694
started this conversation in
Proposals
Replies: 1 comment 2 replies
-
@Sergio0694 we'll have to figure out how we demo this in the sample app, as we'll need the extension registered on the sample app itself, eh? It's a more advanced scenario we haven't really thought about how the infrastructure could support, so we'll have to do some thinking or special casing for the demo of this on the UWP sample head. 🤔 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
CommunityToolkit.AppServices
A library and accompanying source generator to make working with AppService much easier 🚀
Simply define an interface:
Then implement it in your desktop extension:
That's it! The source generator will automatically create for you:
That means, the host (the UWP/WinUI 3 app) can literally just do this:
This enables a fundamentally easier, less error prone and much less verbose way to interact with
AppService
APIs 🚀We developed this library for the Microsoft Store, which uses it for all the desktop extension functionaly, and would like to open source it and add it to the Windows Community Toolkit, so that it can benefit all developers using UWP and WinUI 3. This can be used both to support UWP applications needing a desktop extension component to escape the sandbox (like the Microsoft Store is doing), as well as both UWP and WInUI 3 apps using
AppService
to connect to other applications registered as extensions.Additional features
The library comes bundled with:
IProgress<T>
values across processesCancellationToken
values across processesAPI breakdown
Beta Was this translation helpful? Give feedback.
All reactions