Report on Project as well as VIs

[James_W]

We have the VI reporting Palette and it works very nicely for putting together documentation about VIs that we are using.

But what happens if we want to make a report that details ALL of the files in a project? We have to take a very convoluted route to get the list of files (Project>File information only lists the NI filetypes used in the project and not *.doc;*.jpg etc - these may be neccassary for the project when deployed)

It is possible to programmatically create this list using Property nodes, etc and create the list of dependencies if you start getting fancy.

But try documenting how a build specification was setup so someone else can ensure they do exaclty the same in 6 months time if the project file has been changed or corrupted...

The XML tags in the lvproj file change all the time and there is no documentation on these

From NI tech support:

"We do not have any documentation (internal OR external) that provides the information about all the XML tags; it simply doesn't exist.  R&D would certainly like this information to be available, and they suggested you post this idea at the Idea Exchange.  If this idea gets enough customer interaction, then we would definitely consider developing this in a future version of LabVIEW."

http://lavag.org/topic/11673-programmatically-build-new-project-problem/page__p__70683#entry70683

In short:

Documenting the Build specifications, the list of Project files and the list of dependencies with the Reporting palette would be a massive feature. to have to run on any project and would allow the ability to create build reports containing lists of VIs and their revision numbers for each release.

(Very important for some of my clients)

Just documentation on the XML tags would allow us to do more stuff like this:

http://forums.ni.com/t5/LabVIEW/How-can-I-set-a-build-specificaiton-s-target-filename-and/m-p/181248...

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.