Hi, we're getting an exception when building project. Problem started recently, after updating NCrunch to version 3.3. Version 2.7 works ok.
Visual Studio 2015, target framework 4.0, no post-build manipulation of assembly.
System.NotSupportedException: Specified method is not supported.
w _Mono.Cecil.MetadataReader.LookupToken(MetadataToken token)
w _Mono.Cecil.Cil.CodeReader.ReadOperand(Instruction instruction)
w _Mono.Cecil.Cil.CodeReader.ReadCode()
w _Mono.Cecil.Cil.CodeReader.ReadMethodBody()
w _Mono.Cecil.Cil.CodeReader.ReadMethodBody(MethodDefinition method)
w _Mono.Cecil.MethodDefinition.<>c.<get_Body>b__36_0(MethodDefinition method, MetadataReader reader)
w _Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TItem item, Func`3 read)
w _Mono.Cecil.MethodDefinition.get_Body()
w nCrunch.Reflection.Cecil.CecilMethod.get_HasBody()
w nCrunch.TestExecution.Frameworks.DefaultClassMethodDescriptionLocator.ExtractClassMemberDataFromType(ReflectedType type, Boolean hashAllMethods)
w nCrunch.Compiler.StaticManipulation.BuiltAssembly.(ReflectedAssembly , IDictionary`2 , TestFrameworkDescription[] , Boolean )
w nCrunch.Compiler.StaticManipulation.BuiltAssembly.ExtractClassMethodData(TestFrameworkDescription[] applicableTestFrameworks, IDictionary`2 codeFileIDsByFilePath, Boolean hashMethods)
w nCrunch.Compiler.RemoteBuildRunner..()
w nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
w nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters , FilePath , BuildOutput , DirectoryPath[] , FilePath[] )
w nCrunch.Compiler.RemoteBuildRunner..()
w nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
w nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters )
Do you have any suggestion how to deal with this?
Thanks in advance.
Remco NCrunch Developer
#9839
24 Feb 2017 11:14 UTC
Hi, thanks for sharing this issue.
This problem is likely being caused by an IL sequence that NCrunch isn't designed to handle. It may be possible to work around this problem by turning off the 'Instrument output assembly' setting for this project.
Are you able to share with me a project that can reproduce this issue? Unfortunately it will be tough to track this down without a way to make it happen for myself.
This problem is likely being caused by an IL sequence that NCrunch isn't designed to handle. It may be possible to work around this problem by turning off the 'Instrument output assembly' setting for this project.
Are you able to share with me a project that can reproduce this issue? Unfortunately it will be tough to track this down without a way to make it happen for myself.
Post a reply
Log in to reply.