Benchmarks referencing TestAdapter fail to build with OS-specific TFMs

[molesmoke]

Attempting to use the TestAdapter with a project using an OS-specific TFM such as
<TargetFramework>net8.0-windows</TargetFramework>
gives an error when trying to run the benchmark through the test explorer:

D:\BenchmarkTest\bin\x64\Release\2cab09cb-454b-49b3-b8fb-d898d2a7f2df\BenchmarkDotNet.Autogenerated.csproj : error NU1201: Project BenchmarkTest is not compatible with net8.0 (.NETCoreApp,Version=v8.0). Project BenchmarkTest supports: net8.0-windows7.0 (.NETCoreApp,Version=v8.0)

[molesmoke]

I tried to add a custom entry point and config to specify the TFM explicitly, but got the same error:

public static class Program
{
    sealed class CustomConfig : ManualConfig
    {
        public CustomConfig()
        {
            AddJob(Job.ShortRun.WithToolchain(CsProjCoreToolchain.From(
                            new NetCoreAppSettings(
                                targetFrameworkMoniker: "net8.0-windows",
                                runtimeFrameworkVersion: null,
                                name: "net8.0-windows")))
                                .AsDefault());
            AddLogger(ConsoleLogger.Default);
            AddColumn(TargetMethodColumn.Method, StatisticColumn.Iterations, StatisticColumn.Mean, StatisticColumn.Max);
            AddColumnProvider(DefaultColumnProviders.Params);
        }
    }

    static void Main(string[] args)
    {
        CustomConfig config = new();
        _ = BenchmarkRunner.Run(typeof(Program).Assembly, config, args);
    }
}

[timcassell]

You can use a Config attribute https://benchmarkdotnet.org/articles/features/vstest.html#setting-a-default-configuration
Or you can disable the generated entry point <GenerateProgramFile>false</GenerateProgramFile>

[molesmoke]

@timcassell Ah, yup, the Config attribute does work, but I was trying to do it just via a custom entry point to avoid hitting problems from #2500. If I do both the Config attribute and <GenerateProgramFile>false</GenerateProgramFile> then everything is OK - my bad

[adamsitnik]

cc @caaavik-msft

[NickeManarin]

@timcassell Ah, yup, the Config attribute does work, but I was trying to do it just via a custom entry point to avoid hitting problems from #2500. If I do both the Config attribute and <GenerateProgramFile>false</GenerateProgramFile> then everything is OK - my bad

Hi, do you mind explaining what you did?
I'm using VSTest and I need to run targetting net9.0-windows10.0.17763.0.

    public class CustomConfig : ManualConfig
    {
        public CustomConfig()
        {
            AddJob(Job.ShortRun.WithToolchain(CsProjCoreToolchain.From(
                            new NetCoreAppSettings(
                                targetFrameworkMoniker: "net9.0-windows10.0.17763",
                                runtimeFrameworkVersion: null,
                                name: "net9.0-windows10.0.17763")))
                                .AsDefault());

            AddLogger(BenchmarkDotNet.Loggers.ConsoleLogger.Default);
            AddValidator(JitOptimizationsValidator.DontFailOnError);
        }
    }

    [Fact]
    public void RunBenchmark()
    {
        var summary = BenchmarkRunner.Run<CustomBenchmark>(new CustomConfig());

        Assert.NotNull(summary);
    }