@Slateman wrote:
My main usage case of labwindows/cvi is creating headless DLLs that work with TestStand (Teststand pulls in the parameters automatically due to the 'special' CVI linker which makes development a lot easier). No other linker/linker settings have that capability...
If that refers to the feature that TestStand automatically knows the parameter names and types of a DLL call, a DLL equipped with a standard Type Library (from .idl file) does the same trick. Used that with Visual Studio a few times, just a bit more work creating the idl file.
