Hi @3steve3

How do you run your benchmarks?

I would expect your host process (what you start from command line) to be non-NativeAOT and work fine, while the benchmark process that does not use the taskbar be NativeAOT and also work fine.

@adamsitnik I'm using this command dotnet run -c Release -f net7.0 --runtimes nativeaot7.0 and this main static void Main(string[] args) => BenchmarkSwitcher.FromAssembly(typeof(Program).Assembly).Run(args);

Based on https://stackoverflow.com/questions/68110207/system-notsupportedexception-in-taskscheduler-when-using-publishtrimmed-net6-0 I suspect that something sets PublishTrimmed to true for your project with benchmarks. Could you please try setting <BuiltInComInteropSupport>true</BuiltInComInteropSupport> as described in https://stackoverflow.com/a/69200541/5852046 for the benchmarks project?

If it does not help could you please try downloading our samples and running them?

git clone https://github.com/dotnet/BenchmarkDotNet.git
cd .\BenchmarkDotNet\samples\BenchmarkDotNet.Samples\
dotnet run -c Release -f net7.0 --filter *Basic*Sleep* --runtimes nativeaot7.0

it works fine on my machine:

I was able to repro by adding <BuiltInComInteropSupport>false</BuiltInComInteropSupport>. Unfortunately, the TypeInitializationException seems to be uncatchable, so I'm trying to figure out another fix.

@adamsitnik Fixed in #2255.

I hit the same issue in my csproj:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net7.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <PublishAot>true</PublishAot>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="BenchmarkDotNet" Version="0.13.5" />
  </ItemGroup>

</Project>

Worked around it by commenting out the <PublishAot>true</PublishAot> line.