02-05-2009 08:34 AM
Not to add another variable to the equation but I find myself always getting lost in trying to organize the project explorer when I work on the same code between two different computers.
Some of you may ask, why would you do that? Well I primarly develop the code on my laptop but then I transfer it to a computer that is located 300 miles away via remote desktop to test my developments. I use build source distribution to gather all the necessary vi files, including those in the user.lib folder.This ends up providing me a single folder of all the vis that I will need that I can just transfer over which is nice.
After testing the application I usually find changes I have to make. Now the problem I run into is that if I make the changes on the remote computer I can't easily transfer those changes back down to the laptop because the folder containing the source distribution is organized differently than the original code folder on the laptop. ie it contains the user.lib files.
One workaround to this I realize is I should copy the user.lib file over to the remote computer and not include that in the source distribution. I could do that but it seems like there should be a more flexible way. I don't know maybe I am overthinking the problem. I am a mechanical engineering turned into a software engineer through LabVIEW so my software development practices are lacking.
02-05-2009 08:57 AM
The easiest answer would be 'don't develop on you test computer'.
The best answer is to use an SCC solution between the two computers, this makes sure you have the same code on both computers.
My advice is not to edit code in user.lib directly. Code inside user.lib is distributed code and should be treated as a 'product'. There are several solutions to this (OpenG Packager or VIPM professional are two I can recommend).
Ton