Forgot to implement the WASDK API for operations related to PackageVolume?

[Gaoyifei1011]

Describe the bug

Forgot to implement the WASDK API for operations related to PackageVolume?

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

是否忘记实现与 PackageVolume 有关操作的 WASDK API 了？

---

As shown in the figure, the API for the operation of the PackageVolume is only found in WINRT, and there is no API corresponding to the WASDK, if I want to operate on the PackageVolume, I need to switch back and forth between the WINRT PackageVolume and the WASDK PackageVolume, which is very troublesome, and I hope the WASDK can bring in the corresponding API.

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

如图所示，有关 PackageVolume 操作的 API 只在 WINRT 中找到，没有找到与 WASDK 对应的 API，如果我想要对 PackageVolume 进行操作，就需要对 WINRT PackageVolume 和 WASDK PackageVolume 来回切换，这样操作非常麻烦，希望 WASDK 能带入相应的 API。

Steps to reproduce the bug

See description

Expected behavior

Add the WASDK PackageVolume API

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

添加 WASDK PackageVolume 有关的 API

Screenshots

NuGet package version

Windows App SDK 1.7.2: 1.7.250513003

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 24H2 (22621, October 2024 Update)

IDE

Visual Studio 2022

Additional context

None

[DrusTheAxe]

Ahhhh. Yes, WASDK's PackageVolume is equivalent to the related methods/properties on the Windows PackageVolume runtimeclass and currently doesn't have most of the PackageVolume related methods on PackageManager:

• AddPackageToVolumeAndOptionalPackagesAsync()
• AddPackageToVolumeAndRelatedSetAsync()
• AddPackageToVolumeAsync()
• AddPackageVolumeAsync()
• GetDefaultPackageVolume()
• MovePackageToVolumeAsync()
• RegisterPackageWithAppDataVolumeAsync()
• RemovePackageVolumeAsync()
• SetDefaultPackageVolume()
• SetPackageVolumeOfflineAsync()
• SetPackageVolumeOnlineAsync()
• StagePackageToVolumeAndOptionalPackagesAsync()
• StagePackageToVolumeAndRelatedSetAsync()
• StagePackageToVolumeAsync()

In short, WASDK's PackageVolume doesn't provide most write operations (Add, Remove, etc) nor a read method to get the default (GetDefaultPackageVolume()).

The driving need behind WASDK's PackageVolume was the new Repair() and IsRepairNeeded(). But fair point, the other operations are desired. Will add this to the backlog for consideration during planning exercises. No ETA but it's on our radar now. Thank you for your feedback!

https://task.ms/57784255

[Gaoyifei1011]

Ahhhh. Yes, WASDK's PackageVolume is equivalent to the related methods/properties on the Windows PackageVolume runtimeclass and currently doesn't have most of the PackageVolume related methods on PackageManager:

• AddPackageToVolumeAndOptionalPackagesAsync()
• AddPackageToVolumeAndRelatedSetAsync()
• AddPackageToVolumeAsync()
• AddPackageVolumeAsync()
• GetDefaultPackageVolume()
• MovePackageToVolumeAsync()
• RegisterPackageWithAppDataVolumeAsync()
• RemovePackageVolumeAsync()
• SetDefaultPackageVolume()
• SetPackageVolumeOfflineAsync()
• SetPackageVolumeOnlineAsync()
• StagePackageToVolumeAndOptionalPackagesAsync()
• StagePackageToVolumeAndRelatedSetAsync()
• StagePackageToVolumeAsync()

In short, WASDK's PackageVolume doesn't provide most write operations (Add, Remove, etc) nor a read method to get the default (GetDefaultPackageVolume()).

The driving need behind WASDK's PackageVolume was the new Repair() and IsRepairNeeded(). But fair point, the other operations are desired. Will add this to the backlog for consideration during planning exercises. No ETA but it's on our radar now. Thank you for your feedback!

https://task.ms/57784255

Thank you very much for your reply. I hope to see the realization of the relevant functions soon

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

非常感谢您的回复，希望能在不久后就能看到相关功能的实现

[DrusTheAxe]

Package options target a package volume via Add/Stage/RegisterPackageOptions e.g.

var options = new AddPackageOptions();
options.TargetVolume = vol;
var pdm = new PackageDeploymentManager();
pdm.AddPackageAsync(pkg, options);

is equivalent to

var pm = new PackageManager();
pm.AddPackageToVolumeAsync(pkg, null, DeploymentOptions.None, vol);

That whittles the PackageVolume gaps to

• AddPackageVolumeAsync()
• GetDefaultPackageVolume()
• GetAvailableSpaceAsync()
• RemovePackageVolumeAsync()
• SetDefaultPackageVolume()
• SetPackageVolumeOfflineAsync()
• SetPackageVolumeOnlineAsync()

[Gaoyifei1011]

Package options target a package volume via Add/Stage/RegisterPackageOptions e.g.

var options = new AddPackageOptions();
options.TargetVolume = vol;
var pdm = new PackageDeploymentManager();
pdm.AddPackageAsync(pkg, options);

is equivalent to

var pm = new PackageManager();
pm.AddPackageToVolumeAsync(pkg, null, DeploymentOptions.None, vol);

That whittles the PackageVolume gaps to

• AddPackageVolumeAsync()
• GetDefaultPackageVolume()
• GetAvailableSpaceAsync()
• RemovePackageVolumeAsync()
• SetDefaultPackageVolume()
• SetPackageVolumeOfflineAsync()
• SetPackageVolumeOnlineAsync()

However, I still hope that all the APIs related to packagevolume can be present in the WASDK. Currently, I have no choice but to use two versions of the APIs simultaneously.

[DrusTheAxe]

However, I still hope that all the APIs related to packagevolume can be present in the WASDK

My comment wasn't about downgrading the value or import, just noting the original list was incorrect and larger than actual

Stay tuned, and thank you for your patience

[Gaoyifei1011]

However, I still hope that all the APIs related to packagevolume can be present in the WASDK

My comment wasn't about downgrading the value or import, just noting the original list was incorrect and larger than actual

Stay tuned, and thank you for your patience

Thanks