Copy DevSetupAgent dependencies (Microsoft.Management.Configuration.*) to the output directory. #2618
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
…) to the output directory.
safmswork
approved these changes
Apr 12, 2024
vineeththomasalex
approved these changes
Apr 12, 2024
dhoehna
approved these changes
Apr 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of the pull request
Build stopped copying Microsoft.Management.Configuration.winmd and Microsoft.Management.Configuration.dll files to the output directory of DevSetupAgent (presumably after changing RIDs in project files). DevSetupAgent.exe does not use those files directly, but DevSetupEngine.exe does.
This change adds copy commands to DevSetupAgent and DevSetupEngine projects to get those files into the output.
Validation steps performed
Tested build from VS and build.ps1 script.
PR checklist