Skip to content

Use only a single TFM for M.E.AI.Eval.Reporting.Console #6148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 18, 2025
Merged

Use only a single TFM for M.E.AI.Eval.Reporting.Console #6148

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6f4842e
Use only a single TFM for M.E.AI.Eval.Reporting.Console
peterwald Mar 18, 2025
01bccb3
Add comment noting the bug,
peterwald Mar 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ...rosoft.Extensions.AI.Evaluation.Console/Microsoft.Extensions.AI.Evaluation.Console.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,9 @@
<PropertyGroup>
<Description>A dotnet tool for managing the evaluation data and generating reports.</Description>
<OutputType>Exe</OutputType>
<TargetFrameworks>$(NetCoreTargetFrameworks)</TargetFrameworks>
<!-- Building only one TFM due to bug: https://github.com/dotnet/sdk/issues/47696
Once this is fixed, we can go back to building multiple. -->
<TargetFrameworks>$(MinimumSupportedTfmForPackaging)</TargetFrameworks>
<RootNamespace>Microsoft.Extensions.AI.Evaluation.Console</RootNamespace>
<!-- EA0000: Use source generated logging methods for improved performance. -->
<NoWarn>$(NoWarn);EA0000</NoWarn>
Expand Down
Loading