News for hackers. Stuff that matters.
Re:Microsoft OCR Library for Windows Runtime by rikkus on Friday September 19, 2014 @05:21AM (#8339632)
I made a C# Console app and added the nuget package. It adds, but there aren't any references. Within the nuget package, though, there is are three subdirectories within 'lib', one being 'win81'.

  packages\Microsoft.Windows.Ocr.1.0.0\lib\win81
Within this, there are 'ARM' 'x86' and 'x64' directories and dlls within them. VS refuses to add them to my project, so I'm guessing they're native and not COM libraries.

Why would I think they might be .NET libraries if they have 'x86' and 'x64' labels? Because C++/CLI has to be compiled to separate dlls, I believe.

Re:Microsoft OCR Library for Windows Runtime by pjmlp on Friday September 19, 2014 @05:28AM (#8339649)
It has nothing to do with C++/CLI, but with marshaling, JIT and NGEN.

When calling native code outside the CLR the runtime needs to know which type of marshaling code to generate.

It also plays a role when using unsafe code blocks in .NET.