Request clarification on 'Tips & Tricks' from NIWeek session onLabVIEW Project

I missed this session (Why I hated but now love LabVIEW Project) and I'm looking at the slides online.  Can someone please give me a paragraph (or so) explanation on the first two 'Tips and Tricks' from this presentation?  It says:  •The right way to include built executables- ‘builds’ virtual folder
- cannot be Auto Populating
•Avoiding the cross-linking nightmare- use the Files View not Windows Explorer
- create an allVIs.vi if none exists
 

Hi mike_nrao, Unfortunately I did not attend this
session either, so I'm afraid I wont be much help..  The first tip
seems to refer to the virtual folder in the Project Explorer called
"builds" as seen on slide 10.  Its a good tip just to keep track of your
builds!   The files view is simply the other tab of the Project
Explorer where you can see the actual file location of the VIs used in
the project (which is VERY useful).  I have also come across a number
of allVIs.vi VIs (thats a mouthful<a href="http://forums.ni.com/t5/util/emoticonspopuppage" target="_blank" class="emoticon-link"><img src="http://forums.ni.com/i/smilies/16x16_smiley-wink.gif" border="0" alt=":smileywink:" title="Smiley Wink"></a> ).&nbsp; Basically you make an allVIs.vi
in your project that simply contains every other VI you have in the
project as a subVI.&nbsp; This way you can look at everything you have
developed at once, check out their context help (which of course you
added documentation for) etc.. &nbsp; It gives you a good overview of what
you have in the project, and can also serve as a temporary custom palette! &nbsp;I know this isn't much of an explination, but it's what I got out of just going through the slides.&nbsp; Hope it helps!

Thanks Brian.&nbsp; Why does it say the 'builds' virtual folder cannot&nbsp;be Auto Populating?&nbsp; Does it mean &quot;should&quot; not?&nbsp; and why?I suppose using the Files View helps avoid cross-linking problems by protecting you&nbsp;from opening a VI with the same name (but different location) as one already in the project.&nbsp; Is that what he's getting at, or is there more to it?

hmm.. not sure.&nbsp; I really don't know why the builds folder &quot;cannot&quot; be auto-populating.&nbsp; I see no problem with it, but maybe I'm missing something.&nbsp; In any case, I think it should read &quot;should not&quot; be. I've tried it and it seems OK.&nbsp; That's really all I've been able to get out of the slides, maybe somebody else has a bit more input (maybe someone who actually attended the session?!).&nbsp;Cheers,&nbsp;

just a thought but....&nbsp; I had a situation once where a build with some dynamically called VIs caused cross linking when it was added to the project - maybe only adding the exe to the project (and not the dynamic VIs that go with it) would get around this - something that is not possible with autopopulating folders.&nbsp; Shaun