Your comments

...and I would like to see the LabVIEW project definition parsed and used as to populate the Source File Settings of a new VIP in the builder. This would save me from having to find all the VIs on disk that are not a part of the distribution and having to manually exclude them.

This is still an issue for me. I have had my package throw up a LabVIEW Warning every time the "dotted" trunk was created. I eventually tracked down the two VIs in the source folder that are not a part of the LabVIEW Project listing (or members of the class structure). I don't want to delete these VIs, I may come back to them at some point, but I know that they're not to be included in the VIP so it would be much easier for me if VIP Builder could analyse the lvproj definition and pre-populate the Source File Settings panel with only those that are included.