AtsushiSuzuki

wait, I'm not now able to handle this issue, so please be patient.

Seems that latest node runtime relies on Visual C++ 2017. Try "npm install clr --msvs_version=2017" with 2017 compiler (http://landinghub.visualstudio.com/visual-cpp-build-tools)

Can you please tell me what exactly happens when used with iPhone 11? Exception at `DepthCapture.Configure` ? I'm guessing that this plugin lacks support for newer device types, such as...

> This, on other hand, does not (TargetParameterCountException, yet this is perfectly legal call): > System.Console.Write('12') This seems as a bug around variable length argument. (System.Console.Write(string format, params object[] args))...

Seems that varargs binding is not working properly. Fixing this will take some time, so, for now please avoid using varargs and use normal binding. (like `System.Console.WriteLine("fmt", [])`)

> This code produces huge memory spike (up to 6GB on my Win10), resulting in SEHException: see #4.

Hi. Do you have any actual problem with this? For example, memory leak or longer startup time? I believe that .NET won't load same assembly twice (though I haven't confirmed)....

Ok, I understood. `clr.init` currently returns global namespace, not an assembly. To get types in specific assembly, we have to modify `GetTypes` (in node-clr.cc) to receive assembly names as parameter.

I'm sorry for not responding. I was a little busy. If you could send me a PR, that would help me. (Even if that PR will not be merged directly,...

Great! node-clr has lib/clr.js as main script. lib/clr.js utilizes clr.node. If you do `require(".")` or `require("lib/clr.js")`, it will have documented APIs.