SVN for PowerBuilder 8.x, 9.x, 10.x and upper

Note: project has been moved to code.google.com/p/pbscc-proxy/

How to install it?

You have to install the following software on client computer:

The SccProxy prompts to be installed into the same directory as TortoiseSVN .

What's new?

2010-02-27 Corrected bug whel special sumbols used in comment (like double quote).
2009-08-01 Added parameter into registry cache.ttl.seconds that defines cache time to live in seconds
The environment variable LC_MESSAGES used only for subversion sessions and not for whole PB session.
Removed deprecated functionality : DDB.
2008-06-22 Removed conflict between several PB instances while opening pipe to svn
Removed a bug when PB hangs while executing svn.
2007-06-04 Just set flag noDDB=1 in installation by default
2007-05-31 Changed LANG variable to LC_MESSAGES to avoid conflict with Sybase client.
2007-03-20 On initialization, set the LANG local environment variable to "en_US" to support localized svn version (normally, after that SVN speaking english in the session of PBSCC).
2007-02-17 Support of the SVN version 1.4.x.
New registry key "checkout.lock". If set to 1 then the object will be locked in addition to the property lock method.
2006-12-03 New: one operation for several objects and additional error logging.
2006-04-26 you can specify svn work directory through registry ( ".svn" or "_svn" ).
2006-04-06 corrected a bug with TEMP environment variable. Great thanks to Stephan Glehn. Shame on me.
2006-03-23 _popen function not used any more because it could work incorrectly in non console applications.
2005-12-03 Removed double comment request. Commit error log is redirected to PB.
2005-05-17 Added information about conflict during svn update.
2005-05-16 PBSCC Proxy published.

Any problems?

Use Issue tracking

Questions?

Use PBSCC discussion group

PBSCC + TortoiseSVN Quick start reference.

PBSCC + TortoiseSVN Quick start reference.

How to start subversion service under windows XP

Simple subversion service under windows.

PbSccProxy in real project

The ASE ISQL is a PowerBuilder open-source project that uses the following tools to manage sources:
- PbSccProxy to work with subversion repository from PowerBuilder.
- PBORCA to build PowerBuilder libraries and executable from sources. So you don't need to store PBL's.

Known problems:

To work with console applications (svn.exe) and to avoid console blinking, proxy creates console on library initialization. Sometimes (I don't know why) you could see it, but it quickly disappears.
Today proxy has a simple parser of ".svn\entries" file. And if tomorrow format will be changed then proxy will not work.
PowerBuilder limits SCC CheckIn command to 25 objects.

Solution: PowerBuilder uses an array of object file names that it passes to a source control system in each of its SCC API requests. The SCC specification does not mention an upper limit to the number of files that can be passed in each request, but the default implementation in PowerBuilder limits SCC server requests to batches of 25 objects.
A PB.INI file setting allows you to override the 25-file limit on file names sent to the source control server in a batched request.
You can make this change in the [Library] section of the PB.INI file by adding the following instruction:
SccMaxArraySize=nn
where nn is the number of files you want PowerBuilder to include in its SCC API batch calls. Like other settings in the PB.INI file, the SccMaxArraySize parameter is not case sensitive.

In PowerBuilder 11 the CheckOut operation could be disabled when object just released (CheckIn or Undo CheckOut) by other user.
This is because PbSccProxy uses local cache for 1 minute (3 min in old versions) instead of requesting real status from svn.
Now you can customize this value through registry cache.ttl.seconds value.
Also you can foce PbSccProxy to request real statuses from svn by using Get Latest Version on required library or target.

Svn work directory:

If you are using a special version of SVN with work directory named "_svn" instead of ".svn"
then you must do the following modification of registry:

Configuration of PB:

The field User ID helps to determine current user. This value used nowhere in process except to check if object was checked out by you or by another user. So you can change this value to edit object checked out by another user.

The Project field should contain the folder where you have made "SVN Check Out" operation:

Local Root Directory is a folder of your PB workspace.

As you can see my project contains two subfolders. You must manually create all subfolders of your project in SVN (if you have some).
The Project folder must be always in status normal

when you are going to work with PB.

How it works:

Today SVN supports native object locking, but this information is stored on server only and not cached in local copy.
That's why I'm emulating locking using SVN properties feature. Properties are cached in the local copy

This means that testscc.pbt is locked by the user dmluinfo2id.

To increase speed, SCC Proxy creates cache folder in the svn work directory:

Each file contains just two lines: revision number and value of lockby property.

If you have any problems:

Use google group http://groups.google.com/group/pbscc or mail at pbscc@googlegroups.com.
To enable debug logging, please spesify a full path in the registry:

All svn commands will be logged into this file.
So you can repeat them from the command shell and see where the problem appears.

Also the file "%TEMP%\pbscc.err" created during "svn update" command.
You can check it to see if you have some specific problems.

top | control panel