Agent 2.39 and PowerBuilder 12.5.1 .NET

[rdojr]

We are evaluating v2.39 for use in PB 12.5.1 .NET, and are experiencing several issues. Our setup is as follows:

PB>Options>Source Control
- Environment
- Checked-in item behavior
- On Save: Prompt for check-out
- On Edit: Do nothing
- Allow checked-in items to be edited: No
- Plug-in settings
- Perform background status updates: Yes

Agent
- Mark files as read-only when not checked-out: No
- Use the built-in SVN client tools: Yes
- Lock files on check-out: Yes
- Use the SVN update status option: Yes
- Cache the SVN status results: No

Problems:
1. Checked-in files can be edited. This is prevented if 'Mark files as read only when not checked-out' is set in Agent; however this causes error 'library locked' when trying to add new objects in PB.

2. Check-out does not automatically get the latest version of an object. A GLV must be done first. Afterwards, PB must sometimes be closed and reopened before the latest version will open for editing.

3. To add a new object, we have to a) check it in b) Use TortoiseSVN to commit the updated .pblx file c) Click No to 'Save changes for .pbwx file' dialog.

Any suggestions?

[jussij]

1. Checked-in files can be edited. This is prevented if 'Mark files as read only when not checked-out' is set in Agent; however this causes error 'library locked' when trying to add new objects in PB.

I think this is PB working as designed as per the MS-SCCI.

I'm not a PB developer but I assume it works like the Visual Studio IDE for which the MS-SCCI interface was designed.

In the Visual Studio IDE to add a new file to the project you first need to check out the project.

Now in Visual Studio the check out is done automatically, but that checkout is still required as changes to the project file itself are needed.

Is there a similar option in PB

2. Check-out does not automatically get the latest version of an object.

That is because you are running with the mark files read only option turned off.

In that read/write mode the files are effectively always checked out, so it is up to the user to manager the files. This mode emulates pretty much how the real Subversion works.

But with that read only option turned on Agent SVN will always do a get latest on behalf of the user.

Afterwards, PB must sometimes be closed and reopened before the latest version will open for editing.

To me that sounds like an issue in PB

3. To add a new object, we have to a) check it in b) Use TortoiseSVN to commit the updated .pblx file c) Click No to 'Save changes for .pbwx file' dialog.

That certainly does sound far too complicated

Any suggestions?

Is there a reason you have PB set to: On Edit: Do nothing

Is there an option to: On Edit: Check out file

As I said earlier, I'm not a PB user but as a Visual Studio user, it has such an option and that is how it works by default.

Basically in Visual Studio, the IDE itself decides when files need to be checked out and it does that automatically on behalf of the user.

Cheers Jussi