0

I have two related questions.

(1) Around 4/2019, Microsoft provided a list of APIs that can be called from packaged Desktop apps. (These are in addition to the API that have the DualApiPartition attribute). Has this changed with the November release, is there a more recent version? Is this list going to expand in the future?

(2) When I build a WinUI 3 + .NET 5 packaged desktop application, the libraries linked in under the predefined project include many Windows APIs that are not in the list. Some of these, such as Windows.ApplicationModel.SuspendingOperation, are clearly UWP API. Others, such as Windows.Graphics.Printing.PrintTaskRequest, seem more general purpose. What is the status of all the API that are available in this project definition, can I call them freely from my packaged WinUI 3 + .NET 5 app? Will these be supported going forward, for example are they going to be supported when WinUI 3 supports UWP (in a year or two)?

Improve this question
2
  • Since WinUI3 is still in preview, you'd better ask to the guys building it: github.com/microsoft/microsoft-ui-xaml/issues Commented Jan 30, 2021 at 15:59
  • Indeed. That occurred to me while writing the question, but I still somehow clicked the button here :-) I have now re-posted it as #4065. Commented Jan 30, 2021 at 16:19
Related questions
7
Native Windows Application Development Options
8
Windows API for VISTA, 7 & Beyond
1
Windows .NET / Win32 UI development
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.