Daily Usage Issues

.NET Core 2.0 support

Started by mathiasv on 6,770 views

Hi,

What are your plans to support the recently released .NET Core 2 bits?

I was able to get NCrunch to run on the VS preview build, however when trying to build a project targeting "netstandard2.0" I get the following:

System.ArgumentNullException: Value cannot be null.
Parameter name: type
   at _Mono.Cecil.ModuleDefinition.Import(TypeReference type)
   at nCrunch.Compiler.StaticManipulation.StaticInstrumentationImportMethodSet..ctor(CustomCecilAssemblyResolver resolver, ModuleDefinition module)
   at nCrunch.Core.PlatformTypes.DotNetCorePlatformType.GetInstrumentationMethodsForFramework(CustomCecilAssemblyResolver resolver, AssemblyDefinition assembly)
   at nCrunch.Compiler.StaticManipulation.BuiltAssembly.Instrument(ComponentSourceLineMap sourceLineMap, IDictionary`2 instrumentationDirectivesByCodeFileId, IDictionary`2 codeFileIDsByFilePath, Boolean proxyProcessIsActive, Int32 componentId, IInstrumentationFilter[] instrumentationFilters, IBuildPlatformType platformType, PerfTracker perfTracker)
   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 )
Hi,

The last I heard, .NET Core v2 was on a timetable for a September release. I'm not sure if things have changed since then.

Integrating with code still under development isn't really feasible, because the code changes faster than it can be tied into. Sorry, I'll need to make an informed assessment of the state of this platform before I can make any commitments. Eventually it will need to happen, some time between now and RTM.
2.0 has been released. I'm running into this issue now. I'm trying to update my library to 2.0 and rely heavily on NCrunch.
The build great. Thanks!

Post a reply

Log in to reply.