1. Yakov Werde
  2. PowerServer
  3. Monday, 16 August 2021 18:35 PM UTC

Hello all,

I've put 100s of PowerBuilder C/S applications into source code control and am completely comfortable with the process.  

I'm about to guide someone in putting a PowerServer code set from the PB IDE into source code control.  I'm wondering are there special deployment descriptors and/or other configuration or descriptor files that should be versioned, if not from within the IDE, then perhaps from the commandline as external dependencies?

Thanks

Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 17 August 2021 08:52 AM UTC
  2. PowerServer
  3. # 1

Hi Yakov, 

To move a PowerServer code set from the PB IDE into source code control, you may just submit the PowerServer project file for source control in the same way as with the traditional c/s applications, and pay attention to the following factors that will work differently:

1. Web server profile configuration.  Note that the Web server profiles are configured outside the application source code. So every member in your team shall configure the Web server profile by himself, and update the Web server profile information in the Client Deployment tab of the project settings ;

2. Database configuration. The database configuration is under source control, but if the database server specified is "localhost", other members cannot access. So, it is recommended that you use the actual IP address of the database server in the project settings. 

3. Deployment version. If the team members all deploy to the same web server, and the deployment version is configured the same, only the app files with the highest deployment version will apply. To avoid conflicts, you may consider to recommend the team members to deploy to his local machine during the development, and arrange designated person to deploy to the shared web server.

I saw the discussion between you and Chris. Yes, it shall be unnecessary to version the C# solution unless you are making manual changes to it and have the changes versioned.

Best regards, Julie

 

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Monday, 16 August 2021 21:37 PM UTC
  2. PowerServer
  3. # 2

what version of powerserver?

 

i use dropbox (maintains versions) to hold the config stuff.  Changes are so few that using a full SCC didn't make sense.  

I haven't changed over to PS2021 yet, so things may change, but probably not.

 

I'll be interested to hear what you end up doing.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 16 August 2021 18:54 PM UTC
  2. PowerServer
  3. # 3

Hi Yakov;

   For PowerServer 2021's C# code generated from PB2021, you would open the C# Code in the SnapDevelop IDE (or VS for that matter) & then check-in the C# code into your SCM repository from there. Of course, you are still welcome to use your SCM's client software utility interface to perform that action as well.

Regards ... Chris

Comment
  1. Yakov Werde
  2. Monday, 16 August 2021 20:26 PM UTC
Thanks Chris,

Please excuse the newbe question But

Since these are 'generated' files, why would they need to be versioned? If not modified wouldn't they be regenerated on every deploy?

Yakov
  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 17 August 2021 02:31 AM UTC
Hi Yakov;

Correct ... You asked how vs why. You might only want to place the C# solution into an SCM if you are making manual changes o the C# code or configuration files of the generated solution so that you can restore them after the next GEN is completed.

Regards ... Chris
  1. Helpful
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.