Skip to content

Bump Microsoft.VisualStudio.Diagnostics.Utilities to a release-branch build to fix SymbolCheck (main) - #16323

Merged
Amaury Levé (Evangelink) merged 2 commits into
mainfrom
fix/symcheck-diagnostics-utilities-main
Jul 30, 2026
Merged

Bump Microsoft.VisualStudio.Diagnostics.Utilities to a release-branch build to fix SymbolCheck (main)#16323
Amaury Levé (Evangelink) merged 2 commits into
mainfrom
fix/symcheck-diagnostics-utilities-main

Conversation

@azat-msft

@azat-msft Azat Mukhametshin (azat-msft) commented Jul 30, 2026

Copy link
Copy Markdown
Member

Forward-port of #16322 to main.

Why

main carries the same stale pin as rel/18.10:

<MicrosoftVisualStudioDiagnosticsUtilitiesVersion>18.3.11401.5</MicrosoftVisualStudioDiagnosticsUtilitiesVersion>

18.3.11401.5 is not a VS release-branch build, so no symbols were ever published for its DLLs. That fails Insertion Symbol Check on every VS insertion - see VS !763202 and bug 3038905, where it reported 4 unarchived files:

  • microsoft.visualstudio.enterprise.aspnethelper.dll
  • microsoft.visualstudio.diagnostics.utilities.dll
  • microsoft.visualstudio.architecturetools.pereader.dll
  • extensions\microsoft.visualstudio.architecturetools.pereader.dll

The property drives three PackageReferences in Microsoft.TestPlatform.csproj (lines 98-100) whose DLLs are bundled into the CLI vsix (...V2.CLI.csproj lines 104-109, PEReader shipping twice). The pin sits right under a comment warning about exactly this:

Make sure you are taking a version from a release branch (rel/d*) in VS. Otherwise there won't be symbols for the dlls in package, and it will create a symcheck bug on re-insertion into VS.

#16322 fixes rel/18.10 (the branch the failing insertion is built from). Without this companion PR, 18.11 would ship the same bug.

Fix

Bump to 18.3.11527.243 - newest stable on the vs-impl feed and already used by MicrosoftInternalTestPlatformExtensions in this same file, so a known-good release-branch build.

One line, covers all three packages and all four files.

Verification

Checked with symchk from VS.Tools.VerifyInsertion.Tools against msdl, per the guidance on bug 3038905:

symchk.exe /s SRV*http://msdl.microsoft.com/download/symbols <dll>

Control - Microsoft.VisualStudio.Interop.dll, bundled in the same vsix and not reported by the failing check - PASSED, confirming the method is sound.

Scan of recent versions of Microsoft.VisualStudio.Diagnostics.Utilities:

Version symchk
18.3.11611.365 FAILED
18.3.11527.243 PASSED
18.3.11524.190 PASSED
18.3.11520.95 PASSED
18.3.11518.184 PASSED
18.3.11517.146 FAILED
18.3.11512.103 PASSED
18.3.11511.245 FAILED
18.3.11510.144 FAILED
18.3.11505.172 PASSED
18.3.11503.203 PASSED
18.3.11429.125 PASSED
18.3.11401.5 (current) FAILED

Symbol publishing is evidently inconsistent across builds, so the version cannot be picked by recency alone - it has to be checked.

At 18.3.11527.243, all three packages pass:

SYMCHK: FAILED files = 0
SYMCHK: PASSED + IGNORED files = 3

(Diagnostics.Utilities, Enterprise.AspNetHelper, ArchitectureTools.PEReader)

The pin at 18.3.11401.5 is not from a VS release branch, so its DLLs have
no symbols on the symbol server and SymbolCheck fails on every insertion.

This property drives three packages - Diagnostics.Utilities,
Enterprise.AspNetHelper and ArchitectureTools.PEReader - whose DLLs are
bundled into the CLI vsix.

18.3.11611.365 is already used for MicrosoftInternalTestPlatformExtensions
in this same file, so it is a known-good release branch build.

Forward-port of #16322 (rel/18.10) so 18.11 does not regress.
Copilot AI review requested due to automatic review settings July 30, 2026 09:46

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR forward-ports the rel/18.10 fix to main by updating the pinned Microsoft.VisualStudio.Diagnostics.Utilities version to a VS release-branch build so that symbols are published and VS insertion SymbolCheck can pass.

Changes:

  • Bump MicrosoftVisualStudioDiagnosticsUtilitiesVersion from 18.3.11401.5 to 18.3.11611.365 in eng/Versions.props.

Comment thread eng/Versions.props Outdated
Comment on lines +58 to +60
a and it will create a symcheck bug on re-insertion into VS.
-->
<MicrosoftVisualStudioDiagnosticsUtilitiesVersion>18.3.11401.5</MicrosoftVisualStudioDiagnosticsUtilitiesVersion>
<MicrosoftVisualStudioDiagnosticsUtilitiesVersion>18.3.11611.365</MicrosoftVisualStudioDiagnosticsUtilitiesVersion>
18.3.11611.365 was chosen because a sibling property already used it, but symchk against msdl shows it has no symbols published - same failure as the original pin.

18.3.11527.243 is the newest version where all three packages pass symchk.
Copilot AI review requested due to automatic review settings July 30, 2026 10:15
@Evangelink
Amaury Levé (Evangelink) enabled auto-merge (squash) July 30, 2026 10:16

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

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

Comments suppressed due to low confidence (2)

eng/Versions.props:60

  • The XML comment has a typo: "a and" should be "and" (extra "a"). Consider fixing it since this hunk is already being touched.
      a and it will create a symcheck bug on re-insertion into VS.
    -->
    <MicrosoftVisualStudioDiagnosticsUtilitiesVersion>18.3.11527.243</MicrosoftVisualStudioDiagnosticsUtilitiesVersion>

eng/Versions.props:60

  • The PR description says 18.3.11527.243 is "already used by MicrosoftInternalTestPlatformExtensions in this same file", but eng/Versions.props currently sets <MicrosoftInternalTestPlatformExtensions> to 18.3.11611.365 (line 76). Please update the PR description or clarify the rationale so reviewers don't assume the version is already proven in this repo config.
    <MicrosoftVisualStudioDiagnosticsUtilitiesVersion>18.3.11527.243</MicrosoftVisualStudioDiagnosticsUtilitiesVersion>

@azat-msft

Copy link
Copy Markdown
Member Author

/azp run microsoft.vstest

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

@Evangelink
Amaury Levé (Evangelink) merged commit 252890f into main Jul 30, 2026
20 of 21 checks passed
@Evangelink
Amaury Levé (Evangelink) deleted the fix/symcheck-diagnostics-utilities-main branch July 30, 2026 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants