Sorry, just to clarify a few points:

• You're using WSL, right? Is it WSL 1 or 2?
• You can run other GUI applications on WSL.
• Which Linux distribution are you using?

Thanks

• version 2
• yes, i'm configured Xming and check this on default x11 programs - xcalc, xclock and firefox
• Ubuntu 20.04.3 LTS (GNU/Linux 5.10.16.3-microsoft-standard-WSL2 x86_64)

message in forum contains two problems,

• XDisplay return zero if you not change parameter XOpenDisplay(null); to content output from $DISPLAY variable from console command
• library .dll not correct working call on linux

please say me if second problem need created to another thread - this critical for my project, i'm cannot testing application

Thanks

Another question: Are you able to run OpenGL applications, such as glxgears?

yes.... may-be i'm run app from VS 2022 (target WSL for debug) and this make problem display cannot auto identity x11, i'm tryed first run application from Virtual Box VM on Ubuntu, but after crash without exception - using debug with WSL from VS 2022

2021-10-14 025315.jpg (124,480 bytes)   

2021-10-14 025315.jpg (124,480 bytes)   

I've been able to run our samples using WSL2 and our 3.1.1 NuGet packages.

However, even though it worked for me, I've made two changes that will be part of the next release:

• We were passing "" as an argument to XOpenDisplay. I've changed the parameter to null. When a null pointer is passed to XOpendDisplay it uses the value of the DISPLAY environment variable. It is working for me using "", but the new code is more correct.
• I've made changes to the OpenGL/GLX/X11 DllImports to explicitly state the version of the so, so that you don't need libGLX.so, just libGLX.so.0 and so on. I could get around this by creating the symlinks, but it's more correct this way.

I didn't see any problems with Noesis_GetCurrentThreadId. The version of libNoesis.so has those functions and they work correctly.