Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 20, 2025

Backport of #115951 to release/9.0-staging

/cc @agocke @jkotas

Customer Impact

  • Customer reported
  • Found internally

Newer versions of VS don't have the same versioning scheme as expected in these targets, so Native AOT will fail to find the native linker without this change (and will not be usable for targeting the NET 9 TFM).

Regression

  • Yes
  • No

Testing

Caught with the SDK tests, fix validated manually.

Risk

Low. Deletion of version check.

Delete unnecessary version check
@jkotas
Copy link
Member

jkotas commented Oct 20, 2025

Have we done any testing to validate that .NET 8 works with latest VS?

@agocke
Copy link
Member

agocke commented Oct 20, 2025

Have we done any testing to validate that .NET 8 works with latest VS

This was caught by SDK tests running with the new VS. That covers some set of functionality. Is there a test suite you think would be better? Should we run a net8 servicing CI run for dotnet/runtime on a machine with only new VS?

@jkotas
Copy link
Member

jkotas commented Oct 20, 2025

If this gets covered by a .NET SDK test, it is good enough. I was worried about the scenario being completely broken without us knowing.

@agocke agocke added the Servicing-consider Issue for next servicing release review label Oct 21, 2025
@agocke agocke added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 3, 2025
@agocke agocke merged commit ea23724 into release/8.0-staging Nov 3, 2025
116 of 118 checks passed
@agocke agocke deleted the backport/pr-115951-to-release/8.0-staging branch November 3, 2025 18:24
@github-actions github-actions bot locked and limited conversation to collaborators Dec 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants