-
-
Notifications
You must be signed in to change notification settings - Fork 990
Add support for <UseArtifactsOutput>true</UseArtifactsOutput> #2466
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.
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
Comments
craigktreasure
added a commit
to craigktreasure/Treasure.Utils
that referenced
this issue
Nov 17, 2023
This change adds support for .NET 8. Unlike similar PRs in my other repos, it does not enable artifacts support yet due to an issue with [benchmarkdotnet](dotnet/BenchmarkDotNet#2466).
craigktreasure
added a commit
to craigktreasure/Treasure.Utils
that referenced
this issue
Nov 18, 2023
This change adds support for .NET 8. Unlike similar PRs in my other repos, it does not enable artifacts support yet due to an issue with [benchmarkdotnet](dotnet/BenchmarkDotNet#2466).
craigktreasure
added a commit
to craigktreasure/Treasure.Utils
that referenced
this issue
Nov 18, 2023
This change adds support for .NET 8. Unlike similar PRs in my other repos, it does not enable artifacts support yet due to an issue with [benchmarkdotnet](dotnet/BenchmarkDotNet#2466).
Any updates? 👀 |
It looks like this will be fixed by #2393. |
Merged
Is there a workaround for v0.13.x? |
@viceice The only workaround is to not use You could also try the latest nightly build. https://benchmarkdotnet.org/articles/guides/nuget.html#nightly |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I've recently updated to the dotnet 8 SDK and I've enabled true.
When running my benchmark
dotnet artifacts/bin/Fantomas.Benchmarks/release/Fantomas.Benchmarks.dll
:It was unable to find the right dll due to the new layout.
Am I missing some configuration? Or is this a gap and can we add support for this?
The text was updated successfully, but these errors were encountered: