User:Steven J. Koch/Notebook/Kochlab/2009/06/26/Feedback96 -- moving to visual source safe

From OpenWetWare
< User:Steven J. Koch‎ | Notebook‎ | Kochlab‎ | 2009‎ | 06‎ | 26
Jump to: navigation, search

Steve Koch 16:14, 26 June 2009 (EDT): I have decided we should go with Microsoft VisualSourceSafe for our versioning system for LabVIEW. This was after trying subversion for a while, and briefly looking at git. I think both of those lose a huge amount of their convenience when using binary files, such as LabVIEW VIs.

Now, I have to figure out a (hopefully) sensible way of moving Feedback96 to a directory system appropriate for the future. The user.lib stuff is the most confusing issue for me. Here's what I'm doing:

Feedback96 Heirarchy
  1. Open Feedback96-main-mx. "Save with options" -> development distribution. preserve heirarchy. This saves 176 VIs. (see heirarchy image to the right)
  2. Moving to new directory in the LabVIEW 7.1 folder
    • I think this is the best place, because it will allow for having multiple versions when / if we upgrade to new version of LabVIEW. It also nicely matches the root working folder for user.lib and other folders
  3. Removing the files in ...development_sjkoch
    • I will need to find these when I next load and compile the program
  4. Checking out entire user.lib directoy. My intention is to overwrite the few files I had to upgrade when I was fixing Feedback96
    • In most cases: Replacing user.lib files with ones I just exported from Feedback96
    • FindTetherCenter.llb -- this is an issue, since I know I've fixed an important bug recently. However, I think the bug was in the vi.lib?
      • Going to keep the version from VSS: NOT replace with feedback96 version
      • Not copying: Get 2-d Array which was moved to general user.lib
      • Not copying four default values VIs
      • String-Remove All -- leaving / has been moved to newer part of user.lib
      • Get VI -- new VI by Richard 2008
  5. Loading Feedback96 in new location, manually finding missing VIs (LV was able to find the user.lib files
    • dve_functions_mm_alp.dll
      • I noticed when copying over DLLs (I think 4 in total) that there are still many "fake" DLLs included. I don't know whether these are necessary (surely PID DLL needs to be updated), but this needs to be taken care of.
  6. Clicked close and "yes" for save and "save subVIs". Had to checkout my development/gradschool directory to save a couple.
  7. checking all into VSS database
  8. Added Versatile Feedback DAQ directory to VSS database and checked out immediately

Opening on desktop computer

/compile warnings Steve Koch 17:24, 27 June 2009 (EDT): I think these warnings are fine. I'm checking out the files, and going to save with the new VI locations and then re-check in.