Well after much trying over the holiday period I've come up with the attached. Very much an experimental work in progress, although it does provide the functionality I was seeking. I couldn't see any posted LV code as I don't have 2009 yet (company has lost the discs!!!), but clues you all gave me in the text of your replies, and in a similar one mesmith relied to elsewhere, gave me enough to think on for myself. There are issues, though. GUIDs are a problem; see the comments in the AppEXEConfig subVI. Also, in the same subVI it would nice to create a custom control that contained a tag name and tag value. You'll know what I mean when you investigate it.
I should add, by way of a disclaimer, I don't do much with projects generally. I only use them to create executables (hence my interest in this area) from a single top level VI, so if my goals seem limited project-wise then that's why. I'm not involved with large multi-developer projects at all. Constructive criticism is very welcome.
Graeme.
Hi Grame,
Thanks a lot for your examples. It helps me by A LOT!
I am not sure your version of LabVIEW, but when I tried it in LV 2009 and I build/run the EXE generated, it give me error:
LabVIEW: File is not a resource file.
The file <filename> could not be loaded
So I did a troubleshooting and found the culprit was one of the TAG Name (in AppEXEConfig.vi), Source[1].newName with value of <filename>.exe. The solution to this problem:
- Remove the element: Source[1].newName
- Or change the extension to .vi instead of .exe
I hope it helps to someone who using it in LV 2009
Programmatically build new project problem
in VI Scripting
Posted
Hi Grame,
Thanks a lot for your examples. It helps me by A LOT!
I am not sure your version of LabVIEW, but when I tried it in LV 2009 and I build/run the EXE generated, it give me error:
LabVIEW: File is not a resource file.
The file <filename> could not be loaded
So I did a troubleshooting and found the culprit was one of the TAG Name (in AppEXEConfig.vi), Source[1].newName with value of <filename>.exe. The solution to this problem:
- Remove the element: Source[1].newName
- Or change the extension to .vi instead of .exe
I hope it helps to someone who using it in LV 2009
Cheers,
w15nu