09-14-2009 03:36 PM
Anyone using QVCS with LabView's integrated source control utilities? QVCS supports SCC API and I have it setup as my default version control tool, but each time I try to configure it in LabView (8.6 or 09) I get an error complainig that the specified path is invalid.
Solved! Go to Solution.
09-14-2009 10:13 PM
09-15-2009 12:18 AM - edited 09-15-2009 12:18 AM
**** message deleted*****
09-15-2009 12:27 AM
09-15-2009 10:01 AM - edited 09-15-2009 10:07 AM
Thanks for the feedback. As it turns out, QVCS v 3.7 and earlier work with the LabView integration. All other later versions do not. I have yet to understand what the reasoning is but I do intend to contact Quma and ask for an explanation. I found a way to trick Labview into setting up using QVCS v 3.7 and then swapping out the older version for 3.9. Here are the steps to follow:
1) Install QVCS 3.7 but do not setup a project.
2) Under Admin->IDE Integration, set QVCS as your default version control tool.
3) In LabView go to Tools->Source Control->Configure Source Control. and setup QVCS as the provider.
4) close Labview and QVCS. Remove all of the QVCS 3.7 files from the program file directory. Replace the files with QVCS 3.9 or later.
5) Restart Labview. Files will check in/out using the newer QVCS.
I have had 0 issues with this method so far. LabView's problems seem to only be associated with the setup of QVCS and not the execution.