Skip to content

Runtime query'able version information #2889

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

Merged
merged 13 commits into from
Sep 7, 2022
Merged

Conversation

DrusTheAxe
Copy link
Member

@DrusTheAxe DrusTheAxe commented Aug 22, 2022

Add new API to query Windows App SDK runtime version in use at runtime

WindowsAppSDK-VersionInfo.h at build-time provides what you're built with, but that's merely a "minimum criteria" what you'll use at runtime when using WinAppSDK framework-dependent (aka as MSIX packages). If you build with 1.2.3 you could run with 1.2.3, or 1.2.4, or 1.2.5, or... This lets you query for what is in use at runtime

See Runtime query'able version information API spec #2893 for the API spec

https://task.ms/37963921

@DrusTheAxe DrusTheAxe added the area-Deployment Issues related to packaging, installation, runtime (e.g., SelfContained, Unpackaged) label Aug 22, 2022
@DrusTheAxe DrusTheAxe added this to the 1.2 milestone Aug 22, 2022
@DrusTheAxe DrusTheAxe self-assigned this Aug 22, 2022
@ghost ghost added the needs-triage label Aug 22, 2022
@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@sachintaMSFT sachintaMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving with minor feedback.

@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@DrusTheAxe DrusTheAxe removed this from the 1.2 milestone Sep 2, 2022
@DrusTheAxe DrusTheAxe added this to the 2.0 milestone Sep 2, 2022
…space change to M.W.AM.WAR (which already exists)
@DrusTheAxe DrusTheAxe modified the milestones: 2.0, 1.2 Sep 2, 2022
@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@DrusTheAxe DrusTheAxe enabled auto-merge (squash) September 6, 2022 05:52
@DrusTheAxe
Copy link
Member Author

Sorry! Our services aren't available right now.

UpdateUnreliableTests.ps1 lived up to its name. Kicking off another build to test the question, "Do you feel lucky?"...

@DrusTheAxe
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@DrusTheAxe DrusTheAxe merged commit 0616493 into main Sep 7, 2022
@DrusTheAxe DrusTheAxe deleted the user/drustheaxe/versionapi branch September 7, 2022 19:47
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)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants