Leaderboard

The QControl Toolkit by Q Software Innovations is an object-oriented and extensible alternative to XControls. Use the QControl Toolkit framework and the QControl Creation Wizard to create QControl Classes and receive the benefits of XControls without the headaches. Take advantage of easy UI logic code reuse. Encapsulate and decouple the UI logic away from the business logic of the main application and from the UI skin. Use wherever the VI Server and LabVIEW object-oriented programming are allowed. Easily extend the capabilities of current LabVIEW controls through access to all properties available at run time. And easily use the toolkit with more complex frameworks like the Actor Framework or other plugin architectures where LabVIEW libraries and packed project libraries are used and where XControls can behave unpredictably. Check it out now on the NI Tools Network here. I also started a thread on the NI Community: UI Interest Group page, here.

LabVIEW doesn't deploy shared libraries to the embedded targets itself (except the old Pharlap based systems). So in my experience you always need to find a way to bring the necessary shared libraries to those targets yourself. One option is to just copy them manually into the correct location for the system in question (/usr/local/lib for the NI Linux RT based systems). Another one is to create a distribution package that the user then can install to the target through the NI Max Software installation section for the specific target. The creation of such a package isn't to difficult, it is mostly a simple configuration file that needs to be made and copied into a subdirectory in the "Program Files/National Instruments/RT Images" folder together with the shared library file(s) and any other necessary files. The OpenG ZIP library makes use of this last method to install support for the various NI RT targets.

You can actually extract a VI from an EXE, but there is a very good chance it won't be useful at all. If you did not enable debugging when the VI was made then you will get a VI with no block diagram, no front panel (in most cases) and no source code. This VI will be a thing that can be ran, but only in that one exact version of LabVIEW it was made for. There will be no VI icon, no description, and possibly no terminal labels (it's been a while since I've done this so I can't remember). This process of pulling a VI out is not like a decompiler. The output isn't like source code, it is more like a DLL that is still binary and still compiled for a specific platform and target. tldr; what infinitenothing said.

Software is like a fart. Yours is ok but everyone elses' stinks.