Missing support for extended unicode path names

[bartwe]

Please use Marshal.StringToCoTaskMemUTF8 to pass path as an utf8 string instead of the letting the default ansi marshal happen in the dllimport.

[CoreyKaylor]

I'm assuming that it might be more ideal to Use the technique described here instead? Or am I missing something?

https://stackoverflow.com/questions/17808003/dllimport-ansi-vs-unicode

[bartwe]

That would require changes to the native side to accept the utf16 widechar string when passing unicode. This would still require changes on the native side but would work correctly by default on linux.