Thanks so much for everyone's help - I appreciate it greatly. I've gone for a combination of options that have resulted in a source distribution of all of the dynamic components. The new Project Explorer has certainly helped me here as it offers a layer of abstraction for the developer - I've created the overall system, and I want my developers to be able to define new and change existing dynamic components without the need to touch the main architecure - I've created an application within an application, and the improvements in LabVIEW 8 have certainly helped. Thanks again - I'm a happy little vegemite! :laugh:
I have much the same thought and same situation as yours. I build a main.vi, it is top level and is to be compiled into an exe. Some other vi will be continuously programmed after that. I want to call these VIs by "open vi by reference". Up till now , these dynamically called VIs don't work after compiling. In dev environment they worked as fine as I've expected. But when it is in an exe, the problem comes out. P.S. These dynamically called VIs indeed have subVIs.
So, could you please tell me more details on how to shoot this problem? Pleeeeease?
Calling an external LabVIEW VI from an EXE
in Application Builder, Installers and code distribution
Posted
I have much the same thought and same situation as yours. I build a main.vi, it is top level and is to be compiled into an exe. Some other vi will be continuously programmed after that. I want to call these VIs by "open vi by reference". Up till now , these dynamically called VIs don't work after compiling. In dev environment they worked as fine as I've expected. But when it is in an exe, the problem comes out. P.S. These dynamically called VIs indeed have subVIs.
So, could you please tell me more details on how to shoot this problem? Pleeeeease?