Some questions to be answered by the Windows App SDK team

[Gaoyifei1011]

Describe the bug

Some questions to be answered by the Windows App SDK team

1. Why don't you provide Microsoft. Windows. Management Deployment namespace provides a full explanation of the API documentation? It has been six months since the API collection was released.
2. Are there future opportunities to provide the Windows App SDK with classes and methods that UWP has limited access to in desktop applications? ShutdownManager, TimeZoneSettings, DateTimeSettings.
3. Why not provide improved FilePicker, FolderPicker, etc., in the Windows App SDK? These selectors are commonly used by developers, and the classes and methods provided by WinForm are currently inelegant when called directly through the COM interface or using WPF.
4. Why not provide the user's common SystemTray function in the Windows App SDK?

需要 Windows App SDK 团队回答的一些问题

1. 为什么不提供 Microsoft.Windows.Management.Deployment 命名空间提供 API 文档的详细解释？截止到这个 API 集合的发布已经过去半年时间了。
2. 未来有机会为 Windows App SDK 提供 UWP 在桌面应用中受限制访问的那些类和方法吗？比如 ShutdownManager，TimeZoneSettings，DateTimeSettings。
   3.为什么不在 Windows App SDK 提供改进的 FilePicker，FolderPicker 等等？这些选取器是开发者经常使用的，目前直接通过 COM 接口调用或使用 WPF，WinForm 提供的类和方法很不优雅。
   4.为什么不在 Windows App SDK 中提供用户常用的 SystemTray 功能？

Integration of WinUI issues in this place
WinUI 问题的整合在这个地方
microsoft/microsoft-ui-xaml#9964
microsoft/microsoft-ui-xaml#9946

Steps to reproduce the bug

None

Expected behavior

None

Screenshots

None

NuGet package version

Windows App SDK 1.6.0: 1.6.240829007

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 22H2 (22621, 2022 Update)

IDE

Visual Studio 2022

Additional context

None

[DarranRowe]

For 3, I will ask a counter question. While there has been some posts about fixing the UWP pickers, I haven't seen much of a fuss about implementing a new set of pickers in the Windows App SDK.
The last time this happened, I even mentioned that to really help, someone should make a feature request for pickers in the Windows App SDK and then get as many people as possible to react to it as possible to show there is a lot of support for this. But that feature request never happened.
So he counter question is, what demand is there for these pickers? If the pickers are on Microsoft's roadmap, what reason is there to make them high priority?
It is currently very hard to tell the difference between a few scattered people who just want to grumble and the demand being there but nobody is willing to do the work to make this known. Well, that is enough devil's advocate for one day, but remember that customer demand is everything.

[mominshaikhdevs]

For 1, yes the WASDK docs team is responsible.
For 2, file a WASDK API request for the same.
For 3, upvote #8.
For 4, file a WASDK API request for the same.

[Gaoyifei1011]

For 1, yes the WASDK docs team is responsible. For 2, file a WASDK API request for the same. For 3, upvote #8. For 4, file a WASDK API request for the same.

2 link:#4253
4.link:#4063

[DrusTheAxe]

For 1 it's addressed; docs are available

P.S. 1 is redundant with Hope for Microsoft.Windows.Management.Deployment under the namespace all API to add the API documentation #4253 which noted docs are available

For 2 and 4 please create a feature request issue (as mominshaikhdevs noted)

For 3 see Improved StorageFile APIs #8 and add your input and vote. Or if there's a different aspect to your request pleas create a new feature request issue with your details.