Support for running in-process in the same original thread

[Youssef1313]

BenchmarkDotNet/src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/InProcessNoEmitExecutor.cs

Line 59 in 01d9b78

var runThread = new Thread(() => exitCode = ExecuteCore(host, executeParameters));

Currently, benchmarks always run on background thread. It would be great if a new Toolchain and Executor are run on the same thread, or a property is added to existing toolchains/executors to control whether a background thread is created or not.

[moritz-mg]

Actually, just came across this today - we need to benchmark with a native database ORM (Realm), which requires that its instance is created on the same thread that runs the code.
This fails with benchmarkdotnet as-is right now.

[timcassell]

Actually, just came across this today - we need to benchmark with a native database ORM (Realm), which requires that its instance is created on the same thread that runs the code. This fails with benchmarkdotnet as-is right now.

Can't you just set it up in [GlobalSetup] (and tear it down in [GlobalCleanup])?

[adamsitnik]

This fails with benchmarkdotnet as-is right now.

With the default toolchain no threads are being created and every benchmark is executed in a dedicated, standalone process.