Hi Guys, The LabVIEW project I have been working on for a number of years by now has always been a 'one man show'. I was the only one working on it and the project sat on my hard drive of my only workstation. Now I have a challenge: I am getting a new colleague and we should both be able to work on it simulataneously.It's pretty clear I need a source code control (SCC) system and according to NI's documentation (http://www.ni.com/white-paper/4114/en/) Perforce is still the recommended system. The documentation is lacking however and I'm not talking about Perforce's own documentation (which is pretty good). The 'official' documentation on how to use Perforce with LabVIEW is IMHO too old and limited: https://decibel.ni.com/content/docs/DOC-3203There are a number of issues with that page: - It's a webpage from 2009, converted to PDF and among others the screenshots show an old, Windows XP version of P4V. The current version of P4V is very different.- The section 'Licensing and Compatibility' is out of date: the current version has a limit of 20 users or 20 workspaces (not 2 users, 5 workspaces).The Perforce server is now called Helix Versioning Engine (P4D).- The first paragraph in section 'Installation and Repository considerations' can be removed, Perforce now does provide a standard uninstaller. The biggest issue however is that I'm missing a more extensive howto on how exactly to setup a multi-user LabVIEW environment. There are more steps involved than are written in the PDF. One example: Perforce Versioning Engine by default allows everyone to create their own account and also has write permissions set to everyone. It's very important to quickly change this and raise the security level to at least 2 (password protection). Of course this is mentioned in the 200+ page manual, but it's easy to miss. Another gotcha: directories with '#' in the name (e.g. c#source) will cause problems. By lots of trial and error I have managed to setup a depot on a separate Windows 2012 server, create users, set permissions, create a workspace on my laptop and link it to the depot. I have played around a bit with text files (check out, change, submit) and this works. I still have some questions before I upload my existing 5 GB+ LabVIEW project folder to the depot: - What is the correct order for uploading an existing LabVIEW project to the depot for the first time? My guess would be: create a local workspace (e.g. c:\localcode), copy/move the LabVIEW project folder to c:\localcode, add and submit the files to the depot, open LabVIEW, configure source control, open the .lvproj file and see if it's SCC enabled.- Are the LabVIEW source control settings specific to each LabVIEW-project or is it a central setting for all projects on my computer?- My colleague has a new laptop with LabVIEW 8.6. How can I setup his computer to use the newly created depot without creating duplicates or conflicts?- Any other tips on working with multiple computers/users on one LabVIEW project? Sorry if this sounds like a rant, but I really want to give Perforce a fair chance and don't want to mess up my existing project.Thank you very much for your time and effort. Paul

LabVIEW

LabVIEW and Perforce documentation out of date?

I don't think there's any need to configure Perforce as a default source control provider in Windows; I currently have two source control systems installed (mercurial and svn) and never set either as a default. In the past I've had both Perforce and Microsoft's TFS, again never set either as the Windows default and didn't edit the registry.

Configuring LabVIEW is as simple as opening the source control options page and selecting one of the Perforce providers. If you select the SCM version you also need to pick a LabVIEW project but it doesn't matter which one.

I have no experience with Teststand, and I'm not sure what you're asking in your last question. Does your compiled application need access to modify the VIs in source control?