Hello, NCrunch fails with the following message in one of our test projects:

System.NotSupportedException: Specified method is not supported.
at _Mono.Cecil.MetadataReader.ReadVariables(MetadataToken local_var_token)
at _Mono.Cecil.Cil.CodeReader.ReadFatMethod()
at _Mono.Cecil.Cil.CodeReader.ReadMethodBody()
at _Mono.Cecil.Cil.CodeReader.ReadMethodBody(MethodDefinition method)
at _Mono.Cecil.MethodDefinition.<>c.<get_Body>b__36_0(MethodDefinition method, MetadataReader reader)
at _Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TItem item, Func`3 read)
at _Mono.Cecil.MethodDefinition.get_Body()
at nCrunch.Reflection.Cecil.CecilMethod.get_HasBody()
at nCrunch.TestExecution.Frameworks.DefaultClassMethodDescriptionLocator.ExtractClassMemberDataFromType(ReflectedType type, Boolean hashAllMethods)
at nCrunch.Compiler.StaticManipulation.BuiltAssembly.(ReflectedAssembly , IDictionary`2 , TestFrameworkDescription[] , Boolean )
at nCrunch.Compiler.StaticManipulation.BuiltAssembly.ExtractClassMethodData(TestFrameworkDescription[] applicableTestFrameworks, IDictionary`2 codeFileIDsByFilePath, Boolean hashMethods)
at nCrunch.Compiler.RemoteBuildRunner..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters , FilePath , BuildOutput , DirectoryPath[] , FilePath[] )
at nCrunch.Compiler.RemoteBuildRunner..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters )

I wonder what can we do -- how to locate the exact code that is triggering this error, for example.

This is something that started to appear with growth of the test project. For the record, we use VS 2015, the test library is for .NET Framework 4.5.2. There is no IL postprocessing, I think.

I wrote this code to test what may be causing it:

var assembly = AssemblyDefinition.ReadAssembly(@"C:\Source\...\test.dll", new ReaderParameters { ReadSymbols = true });
var module = assembly.MainModule;

foreach (var type in module.Types)
{
foreach (var method in type.Methods)
{
try
{
var body = method.Body;
}
catch (NotSupportedException ex)
{
Console.WriteLine($"NotSupported: {method.FullName}");
}
catch (NotImplementedException ex)
{
Console.WriteLine($"NotImplemented: {method.FullName}");
}
}
}

There are lots of methods that throw NotSupported and few that throws NotImplemented. Interestingly, when I gradually remove code from the test project, at one point all the issues disappear, even ones previously reported in code that is still there. Very strange. But, all this happens when I use latest stable Cecil nuget (0.9.6.4), but no exceptions are thrown when running against unstable 0.10.0-beta1-v2. So this is probably an already fixed issue.

I guess I can only hope that you update your Cecil sooner than later after 0.10 stabilizes. :-) This is not critical for us, it affects only one from many projects.