PowerBuilder GET not working

[jwolbeck]

In PowerBuilder 11.5 the option to revert back to an older revision does not appear to work.

Steps:
1) Checkout object
2) Right click Show History
3) Select older revision in the History Log
4) Click the GET button

Message appears at the bottom saying, "The local working copy has been updated to revision: <OLD REV HERE>". However the object inside the PBL does not get updated. The exported file on disk DOES get reverted correctly but it appears that object does not get imported back into the PBL like it should.

This happens on V2.54 and V2.49

[jussij]

Code: Select all

The exported file on disk DOES get reverted correctly but it appears that object does not get imported back into the PBL like it should.

This indicates that Agent SVN has done exactly what it was asked to do, as the file on disk has been reverted as requested

PB is not picking up the fact the file on disk has been been changed, so this is in fact a PB bug.

For example, if you did the some test in Visual Studio you would see it works as expected, only because VS is correctly monitoring the file on disk.

All I can suggest is you raise this with the makers of PB or maybe ask for advice on the PB forum as there might be some sort of work around.

Cheers Jussi

[jwolbeck]

Hmm maybe I should add that we are in PBNative (Not PB.NET) where all files are stored in a pbl and not a folder. It is my understanding that the exported files on disk are not monitored by PowerBuilder. Visual Studio is a different game as each file is stored individually on disk from the start. Other SCC plugins we have used with this version of PowerBuilder do successfully allow us to GET history.

Here is the text our old SCC plugin shows when I GET from history indicating that it did do an import into the PBL:

---------- Source Control
Reloading C:\PathToProject\nvo_connect.sru into PBL
Operation Completed
---------- Done Source Control

I see no text when I get from history using AgentSVN other than what is indicated in your Popup.

[jussij]

I did some more investigation into this and this does look like an issue with Agent SVN

A new beta version of Agent SVN has been created and it should fix this issue.

That new beta version can be found here: http://www.zeusedit.com/agent/bin/asvn-dll.zip

To install this version rename the current dll out of the way and replace it with the one from the zip file.

Cheers Jussi

[jwolbeck]

Thanks, the new DLL solved the issue!

I appreciate the fast responses.