Closed metathinker closed 1 week ago
Please, this needs to be addressed, or people get wasting time using WinUI 3.
Thanks for taking the time to let us know about this and we sincerely apologize for the delayed response. There was information added to these docs in March 2022 about calling from desktop apps, with a link added for more info and examples. If you believe your feedback is still actionable, let us know either directly in this thread or by filing a new Issue and we’ll work to incorporate the suggestions into the documentation. Though the Issue will be marked as Closed, we will monitor any replies that come afterwards so feel free to treat this like an open Issue. Many thanks!
@alvinashcraft Just see the issue. The documentation is vague about
To access this page with a URI, use the ms-settings:appsfeatures-app URI and pass an optional parameter of the package family name of the app.
And nothing with that "optional parameter" we have tried so far worked
Since Windows 10 version 1903 (19H1), some of the static methods in the Windows.System.Launcher class have been callable from a Windows classic/desktop application.
To do this, you need to do the following:
Unfortunately, the only mention of any part of this procedure, or that Launcher is even usable from desktop apps, is on the below-linked page for the LauncherOptions constructor.
I don't think this is sufficient because:
To fix this gap, I would suggest that Launcher's doc pages be revised to mention that Launcher can be used from desktop apps using the above procedure, and as an extra hint, LauncherOptions' main doc page should be revised to say that LauncherOptions implements IInitializeWithWindow and that can be used to allow Launcher to be used from desktop apps.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.