1. Miller Rhodes
  2. PowerBuilder
  3. Tuesday, 9 June 2020 23:20 PM UTC

I have a Powerbuilder 2017 R2 application where the workspace and the application PBLs are in GIT Repo1.

The pfc, pfe, and business layer PBLs are in Repo2.

When I want to change anything in the application, I just commit and push to Repo1 which is what I'm connected to by default.

If I want to change any of the pfc related objects ( pfe or business layer ), I open a separate workspace that is connected to Repo2 which has a dummy target that I can use just to be able to do a full build without errors.

We did this because 4 different applications use the same pfc.pfe, and business ( gbc ) libraries.

This all works fine.  However, when I do a deploy of the application, a bunch of the items in the source controlled

pbls get marked with check marks like they've been modified.

This is very strange and I wondered if anyone else had seen this.

Miller Rhodes Accepted Answer Pending Moderation
  1. Wednesday, 10 June 2020 16:26 PM UTC
  2. PowerBuilder
  3. # 1

I migrated the code up to 2019 R2 and even in 2019 R2 this happened after I did a Deploy using our project file.

 

Comment
  1. Tom Jiang @Appeon
  2. Thursday, 11 June 2020 01:14 AM UTC
Do you have some automated deploy script that directly works on the source file?

If you do a refresh on one of the objects does the checkmark go away?

Can you do a diff and see are there any differences in the code?

If you create a simple test project with one of the objects, are you still able to reproduce the issue?

If you can, please open a ticket and provide a test case so we can further verify the issue.
  1. Helpful
  1. Miller Rhodes
  2. Thursday, 11 June 2020 02:40 AM UTC
I'll try some of these things and report back



Miller
  1. Helpful
There are no comments made yet.
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 10 June 2020 05:13 AM UTC
  2. PowerBuilder
  3. # 2

I can't reproduce the issue on the latest 2017 R3 Build 1915. I suggest that you verify it on the latest 2017 R3 and if you still have the issue, please open a Support Ticket at https://www.appeon.com/standardsupport and also attach a simple PB app to the ticket as a test case.

Many thanks in advance!

Regards,

Tom Jiang

Comment
  1. Miller Rhodes
  2. Wednesday, 10 June 2020 13:02 PM UTC
Thanks Tom. I will try. We are moving to 2019 R2 so I suspect this will resolve when we get there too
  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.