Hello ykozlov,
The problem you are running into here is based on the fact that our licensing code looks to a registry key to find the location of the licenses. Of cource, because Linux has no real notion of a registry, this is the primary problem with licensing on Linux.
However, if you were to create an assembly in Visual Studio on a Windows machine, and then take that assembly and it's dependencies to a Linux machine, the licensing information will already be embedded in the wrapper assembly, so you will have crossed the first hurdle. It is important to note that the Meaurement Studio EULA prohibits the distribution of a wrapper assembly such as this for future development.
The second major hurdle is that many of our libraries are written in managed C++, which is not supported on Mono. Because of this, you will not be able to use 3D-Styles on the user interface controls, and any of the precision timing classes. Because we have done very little testing (essentially no official testing) on Mono, some other things may not work as well, and we do not make any claims that any of it should officially work.
However, if you are willing to accept these limitations, wrapping our controls and libraries in assemblies built on a Windows machine will help you get past the licensing error and on your way to using some of our functionality on Mono.
NickB
National Instruments
