[vs17.14] Include ConfigurationManager in Microsoft.Build.vsix

[AlesProkop]

Fixes #14404

Context

The MSBuild configuration redirects System.Configuration.ConfigurationManager to version 10.0.0.8, but the explicit Microsoft.Build.vsix payload omitted the assembly.

Changes Made

• Include System.Configuration.ConfigurationManager.dll in MSBuild\Current\Bin.
• Increment the servicing version to 17.14.53.

Testing

• ./build.cmd -v quiet /p:RunAnalyzers=false
• Built src/Package/MSBuild.VSSetup/MSBuild.VSSetup.csproj with full-framework MSBuild.

[Copilot]

Pull request overview

This PR fixes a Visual Studio servicing regression where MSBuild’s Full Framework binding redirect for System.Configuration.ConfigurationManager points to MSBuild\Current\Bin\System.Configuration.ConfigurationManager.dll, but the Microsoft.Build.vsix payload did not include that assembly—causing in-proc tasks with ConfigurationManager dependencies to fail to load under the redirected policy.

Changes:

• Add System.Configuration.ConfigurationManager.dll to the Microsoft.Build.vsix payload under MSBuild\Current\Bin.
• Bump the servicing version from 17.14.52 to 17.14.53.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/Package/MSBuild.VSSetup/files.swr	Adds System.Configuration.ConfigurationManager.dll to the VSIX file manifest for MSBuild\Current\Bin.
eng/Versions.props	Increments VersionPrefix to 17.14.53 for the servicing build.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Code Review: [vs17.14] Include ConfigurationManager in Microsoft.Build.vsix

Clean servicing PR. No issues found.

• Version bump (17.14.52 to 17.14.53): Routine servicing increment.
• New System.Configuration.ConfigurationManager.dll entry: Correctly added to the VSIX.
• No NGEN attributes: Consistent with non-hot-path assemblies like Microsoft.Bcl.HashCode.dll, System.Threading.Channels.dll, System.ValueTuple.dll.
• No behavioral changes, so no ChangeWave, tests, or breaking-change concerns.

LGTM - no blocking or major issues.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Expert Code Review (on open) for #14496 · 45.8 AIC · ⌖ 4.99 AIC · ⊞ 5K