[release/7.0] Generate VS.Redist package for ANCM - #44369
Merged
Conversation
Member
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Hi @github-actions[bot]. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge. To learn more about how to prepare a servicing PR click here. |
Closed
2 tasks
wtgodbe
approved these changes
Oct 11, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport of #39140 to release/7.0
/cc @wtgodbe
Generate VS.Redist package for ANCM
Adds VS.Redist package that allows auto-insertion of ANCM into Visual Studio
Description
Adds nonshipping VS.Redist package that allows auto-insertion of ANCM into Visual Studio. Will need a follow-up change in VS, and possibly the release pipeline.
Customer Impact
Makes it less likely we miss updating VS in ANCM when there's a security fix
Regression?
[If yes, specify the version the behavior has regressed from]
Risk
Doesn't change code, just adds a nonshipping package
Verification
Packaging changes reviewed?
When servicing release/2.1