LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SCC with multiple versions of LV

We are currently running software on version 4.1 through 6.1, and are slowly upgrading to 6.1. We are also looking to start using the SCC that comes with LabVIEW and are wondering if having multiple versions is going to cause us problems. If anyone has done this in the past, I would greatly appretiate a response.

Thanks

Eugene
0 Kudos
Message 1 of 4
(2,808 Views)
Hi Eugene,

Keeping the versions straight with multiple devlopers that have different drive and file spec and ONLY USING ONE VERSION of LV can be complicated.

Do you really have people using LV 4.1 working on the same apps as the people with LV 6.1? How?

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 4
(2,808 Views)
I definitely have to agree with Ben. You don't want to be mixing many versions of LabVIEW VIs in Source Code Control. In general, it is definitely best for everyone to be developing in the same version of LabVIEW for any given project.

Matt
0 Kudos
Message 3 of 4
(2,808 Views)
You can set up a SCC master directory for each version of LabVIEW.
However, I highly recommend that each team work within the same
version of LabVIEW.
0 Kudos
Message 4 of 4
(2,808 Views)