Configuring LabVIEW Source Code Control (SCC) for use with Team Foundation Server (TFS)

Publish Date: Nov 09, 2012 | 2 Ratings | 4.00 out of 5 | Print | 2 Customer Reviews | Submit your review

Overview

A source control provider helps you manage software projects and facilitates file sharing among multiple users and multiple software projects. The provider maintains a centralized master copy of project files. As you make changes, you update the master copy to reflect those changes. Team Foundation Server (commonly abbreviated to TFS) is a Microsoft product offering source control, data collection, reporting, and project tracking, and is intended for collaborative software development projects.

Table of Contents

  1. Prerequisites
  2. Configuration
  3. Known Issues

1. Prerequisites

Back to Top

2. Configuration

Configuration in LabVIEW:

In order to use the Team Foundation Server with LabVIEW, open the Options menu by selecting Tools»Source Control»Configure Source Control. Select the Team Foundation Server MSSCCI provider from the Source Control Provider Name list, as in Figure 1.

If the provider does not appear in the listbox, confirm that the Team Foundation Server MSSCCI Provider is installed correctly.

Figure 1. LabVIEW Source Code Control configuration window

Configuration in TFS Server:

When you click OK after choosing the Team Foundation Server MSSCCI Provider, the Connect to a Team Foundation dialog should appear. Enter the URL that corresponds to your Team Foundation Server.

 

Figure 2. Connect to Team Foundation Server dialog

 

Alternatively, you can connect to your Team Foundation Server from Visual Studio 2010. 

  1. From the Team menu, select Connect to Team Foundation Server...
  2. Click the Servers... button.
  3. Next, click the Add button.
  4. Enter the URL that corresponds to you Team Foundation Server and then click the OK button.
  5. At the Add/Remove Team Foundation Server screen, click the Close button.
       

Figure 3. Add/Remove Team Foundation Server in Visual Studio 2010

 

Back to Top

3. Known Issues

  1. When choosing a source control provider from within the Source Control Provider Name list (Figure 1), the Connect to Team Foundation Server dialog (Figure 2) could be hidden. This will make it appear as if LabVIEW is hung. Find the dialog, and after entering the TFS URL and clicking OK, the program will return control to LabVIEW.
  2. If you submit a VI file which is not in the configured local path of the TFS server, it will cause error -2915 (Figure 4). Resolve the issue by moving your VIs to the local path or by configuring the local path to include your current VI working directory.

Figure 4. Error Dialog if VI file is not in the configured Local Path

Back to Top

Customer Reviews
2 Reviews | Submit your review

Needs update to later LabVIEW version  - May 30, 2017

the Article needs to be updated to reflect the later LabVIEW versions and what is needed to use TFS with LabVIEW. you also need to list other error codes reported to support.

TFS with LabVIEW 2011  - Feb 11, 2013

Is there any way to work with TFS in LabVIEW 2011?

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit