Issue 243 in the official library mentions Unity 2018.2 using IL2CPP for all windows builds.
Its needs to be investigated if this will affect this library, or if it only affects callbacks from native libraries (which this one does not use).
It also should be looked into if the latest version of Unity3D can skip the native library wrapper all together and if they have fixed the NamedPipeClient provided by C#. If it does support this, a small check can be included to only use the native library for older versions of unity.
Issue 243 in the official library mentions Unity 2018.2 using IL2CPP for all windows builds.
Its needs to be investigated if this will affect this library, or if it only affects callbacks from native libraries (which this one does not use).
It also should be looked into if the latest version of Unity3D can skip the native library wrapper all together and if they have fixed the NamedPipeClient provided by C#. If it does support this, a small check can be included to only use the native library for older versions of unity.