What steps are necessary to get NCrunch work with more exotic CLR languages?

HI,

From presentation NCrunch features seems excellent.
What steps are necessary to get NCrunch work with more exotic CLR languages?
For example: Nemerle or IronRuby, IronPython etc...


Regards

In theory, if the language supports MSBuild alongside .PDB output and doesn't do anything too crazy, then it should be possible for it to work with NCrunch.

The list of supported languages on the front page of this site is actually only the languages that have been properly tested and I can be certain NCrunch will support.

It may very well work with the more exotic languages out-of-the-box. If you have a strong urge to get NCrunch working for a particular language, I recommend giving it a try and sharing your experiences.

but, how about code editor decorations?
will they work with any language service?

I tesyed using Nemerle, and ncrunch does not detect test methods and does not show bullets.
i am using nemerle with vs2010 integration built from github.
it is an exotic language but is there for the clr....

It seems that building tests with nemerle and ncrunch fails with :

NCrunch: If you are experiencing problems in getting this project to build, have a look at https://www.ncrunch.net/documentation/troubleshooting_project-build-issues

(0): System.ArgumentOutOfRangeException: Non-negative number required.
Parameter name: srcOffset
at System.Buffer.BlockCopy(Array src, Int32 srcOffset, Array dst, Int32 dstOffset, Int32 count)
at Mono.Cecil.PE.Image.GetDebugHeader(Byte[]& header)
at Mono.Cecil.ModuleDefinition.ProcessDebugHeader()
at Mono.Cecil.ModuleDefinition.ReadSymbols(ISymbolReader reader)
at nCrunch.Compiler.ILManipulator.ProcessAssembly(String compiledAssemblyFilePath, Boolean instrumentAssembly, IList`1 referencedAssemblies)
at nCrunch.Compiler.RemoteBuildRunner.#=qX56mtP8NEuUXVDSxD4u_yBa0h9Kphx3hJYjFhXON6l8=(ComponentBuildParameters #=qqQXdliE3cs0Z6h4cY7al$g==, String #=qlSVtuKf9XqFFVEauMfzen2rSebF6xoQ80xjfTGfL_5k=, BuildOutput #=quakya0vsA6xNTpFlaTsKcg==, String #=q0WMk_oyyqB84ymhAED64QwQMMcfEx_iwqSh50U8TI54=)
at nCrunch.Compiler.RemoteBuildRunner.Build(ComponentBuildParameters parameters)

Ok - looks like the library NCrunch is using for instrumentation doesn't recognise the assembly output from the exotic compiler.

There probably isn't much I can do about this in the short term. Still, if this is an open source solution, would you be able to leave me a link to it? I'd like to keep a note to look into it later if I get the chance.


Cheers,

Remco

Hi,

Location https://github.com/rsdn/nemerle

I hope you will have a little time to dwelve into it ;)

Regards