This article presents the configuration process of PowerBuilder 12.6 with TFS 2017 (server) using Team Explorer 2013/2015
This article has four sections:
- Prerequisites.
- Setup Team Explorer 2013/2015.
- PowerBuilder Configuration.
- Complementary Information
1. Prerequisites
- Verify that the DPI font is 96 (100%) .
-
Create a new folder on C: drive (C:\MyApp is my example) and copy your application on it.
IMPORTANT: See Numeral 1 of PowerBuilder Configuration section, about folders structure.
- Install Team Explorer for Visual Studio 2013/2015.
https://my.visualstudio.com/Downloads?pid=1433
-
Install Microsoft Visual Studio Team Foundation Server 2013 & 2015 MSSCCI Provider from
- 32-bit (If PowerBuilder is installed on 32 bit)
- 64-bit (If PowerBuilder is installed on 64 bit)
- Restart the computer after install the complementary software. (recommended)
2. Setup Team Explorer 2013/2015
-
Set up the Workspace on Team Explorer.
Once you hit the Map button you will be prompted to get latest of everything in the collection.
For the last screen select No (recommended).
3. PowerBuilder Configuration
-
Configure a folder structure that becomes the copy of the local work of the PowerBuilder code. Put each PBL into its own folder using the library name. This might seem odd at first but once TFS gets a hold of it and all the objects are in each folder along with the .PBG file it will be a lot easier to work with. So lets say the folder structure looks something like this:
MyApp
MyApp_main
MyApp_Module1
MyApp_Module2
…….
-
Put the target file in the MyApp folder.
-
Modify the target in PowerBuilder so that it can find the PBL’s in their new locations. (Comparing with .Net is like the PBL is the project and the target is the solution.)
-
Connect PowerBuilder to TFS via the MSSCCI provider. Set up the connection by right clicking on the PowerBuilder workspace, select Properties option, and go to the Source Control tab.
Set up the connection (User ID, Project and Local Root Directory) as is displayed in the following image. And choose the “Require comments on Check-In” box. To fill up the fields automatically, press the button located at the right side of ht eProject field.
- Press Yes in the case that Changing Server Workspace window be displayed.
-
Press the “Advanced” button and choose “Check Out” option (yellow color).
Press OK button. And press OK button for the Properties window.
The output area will display the message “Connection to source control established”.
-
Choose the target and select Add To Source Control. “This action will export all the objects out of their PBL’s and create a PBG file which is a manifest of the objects inside that PBL”:.
Some screens will be displayed during the process:
For the Add to Source Control screen, all files must be checked. It is recommended to enter comments for them. Press OK to continue.
Another Check In Files screen is displayed several times during this process. Always press the Check In button.
During the process of adding To Source Control, the application could open a new screen asking to check-in the objects. Always press Yes button.
You are done with the configuration process.
4. Complementary Information
The following links were used as a support for the configuration process documentation.
-
TFS - Requirements and compatibility (Updated: 03/02/2016)
-
Connecting to TFS 2017 using VS 2008/MSSCCI Provider for 2013.
-
Brian Harry's blog / Team Explorer for TFS 2017
https://blogs.msdn.microsoft.com/bharry/2017/04/05/team-explorer-for-tfs-2017/
Your comments are welcome.
Luis Gutierrez
Comments (1)