-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PackageDeploymentManager/PackageRuntimeManager v0 (experimental) #3820
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s supposed to be doing. Oh, Will...)
… baked in. Fixed up the project and added to the solution
…lume implementation
… from 2.0.221121.5 to 2.0.230706.1
…initial test code
…needed functionality
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Build failed due to transient infrastructure error. Trying again |
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
…/WindowsAppSDK into user/drustheaxe/pkgmgr
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
sreading-MSFT
approved these changes
Aug 31, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…out using the OS DynDep APIs w/o breaking older users.
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
cwruss
approved these changes
Sep 1, 2023
…ant to Remove later). Cleanup and other fixups
…o remove if they successfully added (so not to break other tests run in the same process).
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-Deployment
Issues related to packaging, installation, runtime (e.g., SelfContained, Unpackaged)
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PackageDeploymentManager is an evolved and enhanced form of core Windows deployment APIs (e.g. Windows.Management.Deployment.PackageManager). These new APIs will provide much of Windows' functionality with enhancements and improved ease-of-use.
PackageRuntimeManager provides a complementary set of APIs for runtime access. This is particularly important given how a PackageSet can be an abstraction of multiple packages. PackageRuntimeManager makes it easy to use sets of packages via Dynamic Dependencies.
Much of this functionality is possible today with existing APIs, but with more effort or complexity on the developers part.
NOTE: This is an early 'v0' implementation for experimentation purposes to unblock other early development. More functionality and refinements are coming RSN. A full API spec detailing the API surface and behavior will be forthcoming in a future PR (and of course subsequent code changes per outcome of the review. This code is experimental until then).
The API lives under
dev\PackageManager\API
, and the associated tests undertest\PackageManager\API
. All tests pass.This PR also updates the repository to TAEF 10.82.230714001 and C++/WinRT 2.0.230706.1.
TODO:
Future PRs will...