• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Is there SCC API documentation so we can write our own plugin?

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Is there SCC API documentation so we can write our own plugin?

  1. How-to
0
Votes
Undo
  1. Tom Peters
    Tom Peters
  2. PowerBuilder
  3. Tuesday, 12 March 2024 15:08 PM UTC

Good Day!

Our source control vendor is no longer supporting their SCC Plugin for PowerBuilder. We would like to build our own, but I cannot find the API documentation. I found the documentation for using SCC in PB IDE, but not the actual API documentation, if any exists.

This is new territory for us, so please forgive my lack of knowledge here.

Thanks,

Tom

WM_SETTINGCHANGE - how to broadcast using SendMess...
Powerbuilder 22 Runtime issue
Responses (4)
Tom Peters
Tom Peters Accepted Answer Pending Moderation
  1. Wednesday, 13 March 2024 15:25 PM UTC
  2. PowerBuilder
  3. # 1

Thanks, Bruce. This would be great.

Comment
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Wednesday, 13 March 2024 14:25 PM UTC
  2. PowerBuilder
  3. # 2

Second the recommendation to look at Git or SVN (preferably Git).  Also be aware that the plans for PowerBuilder 2025 call for an option to have the IDE store the source code in clear text rather than in PBLs, making them directly accessible without having to go through any kind of plugin.  With the current versions you still need to use the options in the PowerBuilder IDE because it needs to export/import the source into the ws_objects folder when interacting with Git and SVN.

Comment
Load more comments
Roland Smith
  1. Roland Smith
  2. Wednesday, 13 March 2024 17:26 PM UTC
You should be able to return to the PBL way if you use PowerGen or some other similar tool that will import source files into PBL files.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 13 March 2024 18:14 PM UTC
Nope .. it's like PB Classic to PB.NET in version 11.x - a one way "no return" trip. ;-)
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 13 March 2024 22:42 PM UTC
Except that this is a trip that doesn't require code changes, the underlying runtime hasn't changed, no unsupported features, etc. Basically PB.NET was a bad trip... anybody that actually tried PB.NET will know what I'm talking about.
  1. Helpful
There are no comments made yet.
Tom Peters
Tom Peters Accepted Answer Pending Moderation
  1. Tuesday, 12 March 2024 15:52 PM UTC
  2. PowerBuilder
  3. # 3

Thanks, Chris. I am starting to think it's time to switch to Git. laughing

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 12 March 2024 15:56 PM UTC
Yes, GIT or SVN might be a good idea. ;-)
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 12 March 2024 15:44 PM UTC
  2. PowerBuilder
  3. # 4

Hi Tom;

  The old SCM plug-ins were normally using the Microsoft SCC API standard as supplied by MS in their SCC SDK ...

FYI: https://learn.microsoft.com/en-us/visualstudio/extensibility/source-control-plug-in-api-functions?view=vs-2022

Regards .. Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.