Unfortunately Mono doesn't support mixed-mode assemblies such as ClearScript's V8 interface (ClearScriptV8-*.dll). We'd like to redesign that layer eventually, but that effort is not currently planned. ClearScript also depends heavily on the C# Runtime Binder,
an API that Mono doesn't seem to support.

Hi, I'm also looking to use this cross platform and have been looking at alternatives for a while, but so far Clearscript is the only one that does things the way I want it to. It was a real bummer when I noticed it only worked on Windows.

How does V8.NET do it, since their library works on other platforms? What are they doing different?

I was going to compare to see if I could make the clearscript v8 work with v8.net's implementation, but my lack of c++ knowledge would be like climbing a mountain for me.

How does V8.NET do it, since their library works on other platforms? What are they doing different?

​
The difference has to do with the way these projects interface managed code with native code. Our understanding is that V8.NET uses
P/Invoke with the managed and native sides residing in separate assemblies, whereas ClearScript uses
mixed-mode assemblies that house both managed and native code.

Mono doesn't support mixed-mode assemblies on non-Windows platforms, and unfortunately this isn't just a matter of binary packaging. It affects how the marshaling code is written, and this is why creating a Mono-friendly version of ClearScript is not a trivial
task.

Another issue for ClearScript is its reliance on the
C# Runtime Binder, an API that Mono doesn't seem to support, although it does have other APIs that might provide a suitable alternative.

By the way, I stumbled upon this thing called swig (http://www.swig.org/) while looking into using RakNet.
Quote from the RakNet documentation:

What is Swig?

Swig is an application that generates wrapper code for a native DLL to interface with other languages allowing you to use a C/C++ library in one of the supported languages. Currently Swig configuration for RakNet is set up to generate a managed interface that
can be used in managed C# in Windows, as well as in Linux with Mono.

Swig generates a CXX and .h file, which exposes interfaces that can be used by the target language. The CXX file is included when building the C++ dll that the target language uses.

Swig also generates files in the target language for inclusion in the project of the target language to interface with the dll. These are added to the project of the target language.

considering Microsoft is making vNext cross platform I think having this EXCELLENT project cross platform would be awesome. I know, I know, easier said than done but from my user perspective talk is cheap :)