0 I have been helping customers who are implementing Team Foundation Server (TFS) and would like to put PowerBuilder Code into TFS source control. I’m not sure how different this would be in the newest versions of PowerBuilder that support xaml and where powerscript is a.net language. However for the older versions where the customer is still using native PB there are a couple of things you might want to do to make the experience better for all involved.

First let me explain one problem with PowerBuilder and TFS: If you just add the PBL’s in your target to TFS all the exported objects end up in one folder and it’s hard to tell where everything comes from. This may not be a big deal if you never look at the source explorer in Team Explorer, but why wouldn’t you? So here are my suggestions: 1. First set up a folder structure that will become your local working copy of the PB code. I recommend putting each PBL into it’s own folder.

This might seem odd at first but once TFS gets a hold of it and all your objects are in each folder along with the.PBG file it will be a lot easier to work with. So lets say your folder structure looks something like this: MyPBApp Logistics Order Shipping Warehouse 2. Now put your target file in the MyPBApp folder. In.net speak the PBL is the project and the target is like the solution. There is one more level above that (the workspace) but I’m going to ignore that in source control and just keep it local. You will have to fix the target in PowerBuilder so that it can find the PBL’s in their new locations. Kanye West Graduation 320 Kbps Music there. Jarsigner Windows 7 Download more.

Make sure PowerBuilder is connected to TFS via the. You can set up the connection by right clicking on the PowerBuilder workspace, select properties and go to the Source Control tab. Me Ghar Se Nikal Aaya Botal Bhi more. I would also install Team Explorer so you have access to the full feature set of TFS. From PowerBuilder pick your target and select Add To Source Control. This 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.

New in PblDump 1.2. Added support for PowerBuilder 10 unicode libraries; Added conversion Unicode->ANSI and ANSI->Unicode (options 'a' and 'u'); Added ability to export only source when '*.*' mask is specified (option 's'); Added list file support: pbldump -e test.pbl @list.txt.

Now anyone on the team can get latest and open the Target in their local workspace. Make sure to tell everyone to make the local copies of their PBL’s writable. Or they will have to check them out when they check out an object. Trust me it’s easier to make them writable locally.

A PowerBuilder library (.pbl file) is a binary file containing PowerBuilder objects such as DataWindows and functions. Although you can browse all objects in PowerBuilder, and edit the source code when you convert the application from Oracle to SQL Server, it is useful to export a libary to source code and then use a tool to automate the conversion. For example, you can use tool to extract all SQL statements from PowerBuilder source code for assessment, analysis, or conversion. A PowerBuilder library contains PowerBuilder objects that exported to the following files: •. You can also write a PowerScript program to automate export of objects from a library (.pbl file). PowerBuilder provides LibraryExport and FileWrite functions.

For example, to export the DataWindow object d_countries from pb_demo1.pbl library, and save it to d_countries.srd file, you can use the following script: String ls_dw Integer li_FileNum // Export the DataWindow object to string ls_dw = LibraryExport ( 'd: demo pb_demo1.pbl', 'd_countries', ExportDataWindow! ) // Save to the file li_FileNum = FileOpen ( 'd: export pb_demo1 d_countries.srd', TextMode!, Write!, LockWrite!, Replace! ) FileWrite (li_FileNum, ls_dw ) Additionally, you can use LibraryDirectory function to get a list of the objects in a PowerBuilder library, and then call LibraryExport for each object.