Thanks Charlotte, I've received the bug report and confirmed the exception below:
System.Exception: System.BadImageFormatException: Could not load file or assembly 'nCrunch.TestRuntime, Version=4.8.0.3, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea' or one of its dependencies. The module was expected to contain an assembly manifest.
File name: 'nCrunch.TestRuntime, Version=4.8.0.3, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea'
at nCrunch.Core.PlatformTypes.DotNetCore.DotNetCorePlatformType.GetCoverageEventListenerTypeForInstrumentation(CilContext context)
at nCrunch.Compiler.NewStaticManipulation.ImportedNCrunchRuntimeAssembly..ctor(CilContext context, CilManipulationOperation manipulationOperation, IBuildPlatformType platformType)
at nCrunch.Compiler.NewStaticManipulation.BuiltCilAssembly..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Compiler.NewStaticManipulation.BuiltCilAssembly.Instrument(IInstrumentationFilter[] instrumentationFilters, PerfTracker perfTracker)
at nCrunch.Compiler.CilProcessingTasks.CilInstrumentationTask.ProcessTask(IBuiltAssembly builtAssembly, ComponentInstrumentationParameters instrumentationParameters, BuildOutput output)
at nCrunch.Compiler.CilProcessingTasks.ConcurrentCilTaskProcessor.()
I've never seen this issue before. nCrunch.TestRuntime is a .NET 3.5 assembly that is shipped with NCrunch, and I can't think of any reason it would fail to load other than the file being corrupt. Could you try reinstalling the version of NCrunch you're using? I'm hoping this will fix the file and allow instrumentation to continue as normal.