* read the process output in a thread safe way, fixes#1051
* this test started to fail, most probably due to an AppVeyor change
* this test takes a LOT of time and since we have new InProcessEmitToolchain we can disable it
* disable UserCanSpecifyCustomNuGetPackageDependency which is for some reason this test is unstable on Ubuntu for both AzureDevOps and Travis CI
* update dotnet cli version hoping that it's going to help with unstable CI..
* don't set the capacity for StringBuilder hoping that it's going to help..
* remove duplicated logging for MemoryDiagnoserTests
* AccurateAllocations.Nothing duplicates EngineShouldNotInterfereAllocationResults, removing it to save CI time
* CoreRT support is verified by CoreRtIsSupported, we don;t need to run ArgumentsTests for CoreRT (each of them takes 0.5 minute)
* make it work after my recent refactor
* Roslyn Toolchain does not work on .NET Core becasue we don't know which assemblies to reference
* static benchmarks are not supported for out-of-proc toolchains
* use reflection to allow for assembly saving for tests purposes only
* some pedantic renaming
* remove the .dlls after the checks pass in order to avoid file in use exception
* we don't need to mimic DirtyAssemblyResolveHelper in the in-proc toolchain
* make the new InProcessEmitToolchain a default one for -i --inprocess console line arguments
* We can't use Roslyn toolchain for .NET Core because we don't know which assemblies to reference and .NET Core does not support dynamic assembly saving
* target .NET Standard 2.0 only
* don't box ;)
* use DirtyAssemblyResolveHelper in the auto-generated code because it's simply very common case that VS generates wrong redirects..
* disable two tests which fail due to CommandLineParser issue...
* bring Full .NET Framework tests back to life!
* make it possible to build BDN from source on Mac
* there is no way to do tell dotnet restore which configuration to use, we need to handle that for custom build configurations
* perform full build when user provided custom build configuration
* workaround bad assembly binding redirects on our side to keep the users happy ;)
* Duplicates handling for IConfig = big refactor, fixes#360
* handle the case when IExporterDependencies were added by user in a wrong order
* every benchmark case has it's own Config, try to avoid global config which can be incomplete in some scenarios
* print the test output to the console
* refactor
* update dependencies
* Use .NET Standard 2.0 CommandLineParser, Update to net461 for NS2.0 support
* change to the newly released CommandLineParser 2.4.3 with NS 2.0 support
* BenchmarkDotNet as global tool
This resolves#213.
* Set TargetFramework to "netcoreapp2.1"
* Add import for common build properties.
* Docs: BenchmarkDotNet as global dotnet tool