Adam Sitnik

Some hints for the potential contributor: - When I run a sample benchmark like the following: ```cmd cd samples\BenchmarkDotNet.Samples\ dotnet run -c Release -f net6.0 --filter *IntroDisassembly.* --job dry ```...

@franciscomoloureiro great, I've assigned you. Please let me know if you need help.

@YegorStepanov your proposal sounds very reasonable, I like it! @franciscomoloureiro if possible, please take it into consideration

Hi @pr8x > I am wonder if there's a way to skip the building of these native dependencies (tried --no-dependencies to no avail) and provide the prebuild binaries myself? BenchmarkDotNet...

> Does Benchmark.NET have support for a MSBuild toolchain (that doesn't use dotnet build internally)? It does not, but `dotnet build` "should just work" ;) > I tried using InProcess...

Hi @Zhentar Thank you for a great input and appologies for such a huge delay in response. > One thing that would help would be adding an option to use...

> which will contain all the generated files and folders @AndreyAkinshin do you mean only the results (`.csc`, `.html` and etc) and logs (`.log`)? then such change is easy but...

@ViktorHofer Done! As soon as [this](https://ci.appveyor.com/project/dotnetfoundation/benchmarkdotnet/build/0.10.12.430) build is over, you should be able to download `0.10.12.430` version with this new feature from our CI feed. ```xml ``` ```cs [ArtifactsPath(@"C:\here")] [DryJob]...

@ViktorHofer thanks! I will contact you soon about local Core CLR/FX builds

@filipw hi Filip! You should try our InProcessToolchain which does not compile and spawn new processes but instead generates new types using IL Emit. [Here](http://benchmarkdotnet.org/Configs/Toolchains.htm#inprocesstoolchain) is a good description of...