Skip to content

Add netstandard2.0 and net462 TFM support to AmbientMetadata.Build#7463

Open
aykutkaann wants to merge 1 commit intodotnet:mainfrom
aykutkaann:fix/build-metadata-tfm-support
Open

Add netstandard2.0 and net462 TFM support to AmbientMetadata.Build#7463
aykutkaann wants to merge 1 commit intodotnet:mainfrom
aykutkaann:fix/build-metadata-tfm-support

Conversation

@aykutkaann
Copy link
Copy Markdown

@aykutkaann aykutkaann commented Apr 11, 2026

Fixes #7415

Summary

Added netstandard2.0 and net462 target frameworks to Microsoft.Extensions.AmbientMetadata.Build package to match the Microsoft.Extensions.AmbientMetadata.Application package, which already supports these TFMs.

Changes

  • Updated TargetFrameworks in Microsoft.Extensions.AmbientMetadata.Build.csproj from $(NetCoreTargetFrameworks) to $(NetCoreTargetFrameworks);netstandard2.0;net462

Context

The Application package already targets netstandard2.0 and net462, but the Build package did not, preventing usage in projects targeting these frameworks. As noted in the issue, there is no specific code preventing this package from working on these platforms.

Microsoft Reviewers: Open in CodeFlow

@github-actions github-actions bot added the area-ai-eval Microsoft.Extensions.AI.Evaluation and related label Apr 11, 2026
@aykutkaann
Copy link
Copy Markdown
Author

CI failures appear to be unrelated to my change — they are in Microsoft.Extensions.ServiceDiscovery.Dns.Resolver.Tests.TcpFailoverTests, which is a different package from AmbientMetadata.Build. These look like pre-existing flaky tests related to socket/network behavior in the CI environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-ai-eval Microsoft.Extensions.AI.Evaluation and related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Microsoft.Extensions.AmbientMetadata.Build does not support netstandard2.0 and net4x

1 participant