Tim Cassell

It looks like we can support this by setting the `SetTargetFramework` property of the project reference. ```xml TargetFramework=netstandard2.0 ``` Of course, it would still require you to include the framework...

Seems related to #1210

This is already working for Core runtimes. I sent a PR to fix this for Framework in #2370. I'm also aware of classic Mono not being able to rebuild per...

@stephentoub I added [tests](https://github.com/dotnet/BenchmarkDotNet/blob/914ee7187340761594728497a9f0163a1ecddf67/tests/BenchmarkDotNet.IntegrationTests.ManualRunning.MultipleFrameworks/MultipleFrameworksTest.cs) showing that we are recompiling. Can you share a repro of what you are seeing?

Oh I see, that's a separate issue. https://github.com/dotnet/BenchmarkDotNet/issues/1377

Do you know how to pass it to the proper project? I couldn't figure it out. When I tried it without BDN, it was passed to both projects, but with...

> I commented out all job definitions except the last one and it worked as expected. Really? I tried that and got the same result as the job without the...

I see the issue. On each build, by default the binaries are placed in `./bin//`, so with 2 builds using the same configuration and runtime, 1 of them will overwrite...

Disabling parallel builds and using `dotnet build --no-incremental` works if the host is net7.0, but fails if the host is net8.0. [Edit] I was able to get it to work...

I sent a fix #2393 which makes the host runtime no longer matter (unless you need classic Mono or in-process).