Skip to content

MSBuildInstanceSelector: exact Roslyn version equality — SDK servicing skew falls back to a known-broken registration #166

Description

@MelbourneDeveloper

From the multi-agent audit (sidecars/SharpLsp.Sidecar.CSharp/MSBuildInstanceSelector.cs ~166): SDK selection accepts an SDK only when its Roslyn assembly version EXACTLY equals the bundled one; any servicing skew (e.g. bundled 5.6.0.0 vs SDK 5.6.1.0) rejects every SDK and falls back to a registration already known not to satisfy the bundled surface — reproducing the #159 crash-loop class on machines that are actually fine.

Selection should accept any SDK whose Roslyn is >= the bundled surface's requirement (or better: stop depending on the SDK's Roslyn at all now that #159 ships the full bundled set — verify which assemblies still resolve from the MSBuild directory and pin/carry them).

Relates: #135, #159.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions