User Rating: 3 / 5

Star ActiveStar ActiveStar ActiveStar InactiveStar Inactive

This article is a guide to connect Powerbuilder 2017 with TFS. It is important to follow the steps in the order listed in the article.

The prerequisite includes

  • PB17 installed on a local machine.
  • TFS server running with access to the user. A collection is required where the code will be checked in. 

Next follow the below points:

  1. Team explorer 2013 : Yes the first thing needed is to install Visual studio team explorer. I know the first question pop ups in mind is if Visual studio needs to be installed on every machine !! Well the answer is NO. All you need is Team explorer 2013 to access the TFS. Second question is why 2013 ? Well there comes the 32 bit and 64 bit compatibility issues, moreover there is no standalone installer for Team explorer 2015. If you figured out a way to do it with later versions, then mention it in the comments. 

Follow link

You need a Microsoft account to download Visual studio Team explorer. It's a free account and free download, Install the DVD option if it asks. Online installation sometimes causes problems if your computer has pre requisite software missing. 

  1. MSSCCI: The way it works is that PB requires MSSCCI to connect with TFS. Use the below link to download and install it :

Make suer it is 32 bit as PB17 is a 32 bit IDE. 

  1. Add project in Team Explorer:  Open Team explorer 2013 and add project/collection from your TFS server. 
  2. Configure Powerbuilder 2017: Open your workspace in powerbuilder. Go to properties of workspace >> Source Control.
    1. In the source control  system use Microsoft team foundation server. 
    2. Provide your windows login credentials in User ID.
    3. Click on the ellipse button beside Project:. It should automatically select the project you choose in step 3. If not so then do it manually by selecting the TFS server and then server path from the popup screen. 
  3. Add to source control:  Once the Powerbuilder shows in output that source control is ready, right click on the workspace and hit Add to source control. It will ask if if multiple files are to be checked in, press OK. 

You are done with the connection ! Put down the comments mates yes

Comments (13)

  1. Frank Frey

Nice article. Would this also be applicable to PB12.6 classic?

  1. Nasir Ahmad

Yes, It should work for 12.6 classic version and 12.5 as well. 

  1. Vollie Sanders Jr

Question I have is what TFS server version do we need to use, Corp office has TFS2010 and TFS2015. will ether of these work?


Frank, I am writing a similar document for PB 12.6 with TFS2017 (server), using VS2015. I hope to share it soon. My initial recommendation for you, is to create a folder for each PBL.

  1. Nasir Ahmad

TFS2015 server will work as per my knowledge since MSSCCI and team explorer i tested was for TFS 2013, which worked for TFS 2017.  

For earlier versions of TFS you test and find MSSCCI, Team explorer which are compatible with that version. 

  1. Van Sederburg

Worked perfectly!

  1. Armeen Mazda

Another way to use PB 2017 with TFS is to switch the repository from the legacy TFVC to Git. With recent versions of TFS the default repository is actually Git, and Microsoft recently acquired GitHub. The advantage of switching is that PB 2017 natively interfaces with Git rather than using the legacy MSSCCI interface, which gets you support for more source control features and faster performance of source control operations.

  1. saim thomus    Armeen Mazda

The local interface of the source control frameworks is utilized (rather than MSSCCI), wiping out the need and reliance on outsider modules. The PowerBuilder PBLs still stay as twofold libraries in the PowerBuilder IDE. At the point when a PowerBuilder workspace is transferred to the SVN or Git server, an undertaking is made for the workspace. The structure of the venture in the server (and also in the nearby store) is nearly the equivalent as the one in PowerBuilder IDE, then again, actually the genuine.PBL records are not transferred to the task. Rather, a sub organizer is made in the venture for each PBL, and the sub envelope contains all the source documents of the relating PBL. All the usually utilized SVN/Git directions will be upheld, including Connect to Workspace (identical to Checkout in SVN and Clone in Git), Add to Source Control, Commit, Revert, Update (SVN), Pull (Git), Push (Git), Delete, Copy and Move. Establishment of an SVN/Git customer is simply discretionary, yet doing as such may give extra source control administration includes that benefits your undertaking, for instance spreading and blending. for any Telstra issue How to setup Telstra Wi-Fi connection

  1. iliyan iliev

MSSCCI dosn't works with TFS 2018 ! Any idea how to use tfs 2018 ?!

  1. Nasir Ahmad    iliyan iliev

Is your team explorer connecting to TFS? which version of visual studio team explorer are you using ?

I would recommend you to move from TFVC to Git as recommended by Armeen Mazda in above comment.

  1. iliyan iliev    Nasir Ahmad

I'm use VSTE 2017

  1. Alain Van den Abbeele    iliyan iliev

It doesn't work with VS2017.
You need VS2013 or the free Team Explorer 2013.
Also configure your workspace in TFS as Server workspace!

  1. Alain Van den Abbeele

It works perfectly on Azure DevOps also!
But only with VS2013 or Team Explorer 2013.
TFS workspace must be configured as Server workspace.

There are no comments posted here yet