microsoft / microsoft/WindowsAppSDK

Bug title:When will the API not yet implemented by PackageDeploymentManager be supported?

Open
#5,533 0 comments 0 reactions 1 assignee View on GitHub

@DrusTheAxe is already working on this.

Since Jan 12, 2026.

area-PackageManagement
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Describe the bug

When will the API not yet implemented by PackageDeploymentManager be supported?

---------------------------

什么时候支持 PackageDeploymentManager 尚未实现的 API?


When you call PackageDeploymentManager.ResetPackageAsync(), PackageDeploymentManager.RepairPackageAsync() and other related methods, the exception NotImplementedException is triggered. Looking at the DLL function entry point, we see that the corresponding function already exists on 26100, so when will the Windows App SDK support the API?

---------------------------

调用 PackageDeploymentManager.ResetPackageAsync(), PackageDeploymentManager.RepairPackageAsync() 等相关方法时,会触发异常 NotImplementedException 尚未实现,查看源代码后发现是尚未支持相应的 API。通过查看 dll 函数入口点发现,在 26100 已经存在相应的函数,所以问一下 Windows App SDK 什么时候支持该 API?


Image

Image

Image

Steps to reproduce the bug

See description

Expected behavior

Add PackageDeploymentManager.ResetPackageAsync(), PackageDeploymentManager.RepairPackageAsync() API support

---------------------------

支持 PackageDeploymentManager.ResetPackageAsync(), PackageDeploymentManager.RepairPackageAsync() API

Screenshots

No response

NuGet package version

Windows App SDK 1.7.3: 1.7.250606001

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 24H2 (22621, October 2024 Update), Insider Build (xxxxx), Windows 11 version 23H2 (22631, November 2023 Update), Windows 11 version 22H2 (22621, 2022 Update), Windows 11 version 21H2 (22000), Windows 10 version 22H2 (19045, 2022 Update), Windows 10 version 21H2 (19044, November 2021 Update)

IDE

Visual Studio 2022

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.