LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Capture to file the information shown in the project explorer "Files" tab?

Using the LabVIEW project explorer, if I go to the "Files" tab and select "Expand All" is there a way to capture the information shown other than a bunch of screen shots?  I'd like to get a listing of all the files used by the project along with the locations where they are stored.

0 Kudos
Message 1 of 18
(3,531 Views)

!1-1.png

 

Or you could just open the *lvproj file with any text editor or web browserSmiley Very Happy


"Should be" isn't "Is" -Jay
Message 2 of 18
(3,524 Views)

At least in LV2013, under Project/File Information, you can export all the filepaths as a text file.

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 3 of 18
(3,523 Views)

Project Explorer Menu

Click on

Project \ File Information

 

Then you can export file paths

 

Project File Info.png

Omar
0 Kudos
Message 4 of 18
(3,519 Views)

Jeff had the best solution though I had to tweak his code a bit to actually get a list of all the files.

 

Project File List.png

 

I could get something like this to work for me. Thank you.

 

As for the other two suggestions to use the export-filepaths option, that does not work for me. It only exports the top-level file/VI names along with the project name (in the case of the project of interest, only four files are listed, when I'm expecting to instead see close to 500).

0 Kudos
Message 5 of 18
(3,505 Views)
And opening that lvproj in ie?

"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 18
(3,490 Views)

@JÞB wrote:
And opening that lvproj in ie?

           looks really ugly! 

 

Nothing but line after line of run-on ASCII text and while there are file paths buried in there, there is at least as much other stuff that are not paths.

 

0 Kudos
Message 7 of 18
(3,485 Views)
It is xml

"Should be" isn't "Is" -Jay
0 Kudos
Message 8 of 18
(3,480 Views)

I had tried a copy of the file with both .htm and .html extensions and it was quite ugly when opened. A  .txt file extension looked a bit better but there were still large areas of run-on text.  Changing the extension to .xml brings more order to it but that only puts lipstick on the pig.  It's still ugly.

 

I really do like the first answer. I've already got a working VI that presents a list of all open projects and when one is selected it goes through an generates an array of all files used. Duplicates are removed from the array and it's all ordered/sorted by path. I can then browse through the array list or cause it to be written to a text file.

0 Kudos
Message 9 of 18
(3,467 Views)
Open with from windows explorer. Don't change the extention

"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 18
(3,461 Views)