08-16-2021 08:52 PM
Hello:
Is there a way to make the LabVIEW project file included as part of the exported files when doing "Source" Export to new location via the LabVIEW Source Export Build Specifications node?
I did this export just now but the Project file went missing.
When I copied the Project file over as unopened copy, and tried to open it, that project file referenced all VIs from the source location.
How can I resolve this.
Work-Around for Now
================
Looks like the only workaround for now is to relocate the exported hierarchy under the same hierarchy paths on the next PC to which this project will be moved-to. So that the project reference paths remain same.
Any help to get a Project file to reference the exported relative path is appreciated.
Anthony L.
Solved! Go to Solution.
08-17-2021 12:53 AM
OK:
I tried the ZIP file option to distribute the Source code and this option did save the Project File correctly, allowing reference of project contents via relative path and thus the project file worked OK when moved to a different PC at a different top level folder name.
Thus the ZIPPED source distribution option was the way that resolved the missing Project file challenge when duplicating the LabVIEW project source code..
Anthony L.
08-17-2021 11:44 AM - edited 08-17-2021 11:44 AM
@Anthony_L wrote:
OK:
I tried the ZIP file option to distribute the Source code and this option did save the Project File correctly, allowing reference of project contents via relative path and thus the project file worked OK when moved to a different PC at a different top level folder name.
Thus the ZIPPED source distribution option was the way that resolved the missing Project file challenge when duplicating the LabVIEW project source code..
Anthony L.
That's UGLY, but I'm glad it worked!
Edit: didn't mean to imply that it was wrong, just that the solution ugly because it shouldn't have to be this way.