Where do YOU store YOUR LabVIEW test vis? [copied from WNY LUG from KParfitt]

[srogers]

Someone from the Western NY LUG posted a great discussion on file management/storage and I thought someone in WPA might have some advice...

[from KParfitt on Western NY LUG]:

Hello,

I'd like to know where in the directory structure people put their LabVIEW test programs.  For example, at my company, we have a large reuse library that resides at C:\Program Files\National Instruments\LabVIEW x.x\user.lib\.  We also store LabVIEW vis that are specific to a unit-under-test in a "programs" folder within user.lib.  This works fine, but causes an issue with the way we archive and control our source code.  If the source code database directory structure matches the PC hard drive, then every test station gets everyone's uut-specific test code when they get the latest from the database.  Even if it is not needed.  If the uut-specific code is in another location in the database (not under user.lib) then the user has to know to put it in the programs folder.

Sorry if this is hard to follow!    Anyway, where do YOU put them??

[#2]

We store everything in an SVN repository based on project.  This is less efficient than an actual library but it's backed up and secure.  Also, anyone can get the to the files with access.

[BJD1613]

We separate our user.lib from our actual projects.  We (Philips Respironics) store our applications under C:/labview/project/<your project name>.  This project folder can have many projects depending what you are working on.  Under each project folder we have the following sub folders:

1. Source - where the actual code is stored

     a. CTLs - any typedefs or custom controls used

     b. GBL - any Globals used

2. Documentation - where all of the project documentation is stored

3. Release - where any exes/installers are stored

4. Code Review - where all of our code review documents are stored

5. V&V- where all of our V&V documentation is stored.

The main directory of C:/labview/project/ maps directly to our Visual Sourcesafe database.  So you can go and get the latest from any project you want and it will bring it into the project folder.  We like to stay away from the LV program files folders.

Our user library is a separate directory in our VSS database (named user.lib).  This separates projects from reusable code.   Keeping everything in uniform directories is essential.

Thanks

BJD1613