1. Steve Sagodi
  2. PowerBuilder
  3. Monday, 15 April 2019 16:14 PM UTC

Hi, I'm hoping somebody can educate me on the difference between the following actions below.  I've reviewed a bunch of documentation but its wasn't very definitive if you should do a Full Build before executing the Deploy.

Powerbuilder 2017 R2 - Classic client server app

1. Run menu - Full Build (target)

2. Open project, Deploy

 

thanks,

Steve

Olan Knight Accepted Answer Pending Moderation
  1. Monday, 15 April 2019 20:07 PM UTC
  2. PowerBuilder
  3. # 1

Bottom line:

If you have changed your ancestor code OR you've made a lot of changes, then do a full rebuild and a full deploy.

Otherwise just BUILD the objects that were changed and deploy those PBDs only.


Olan

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 15 April 2019 17:10 PM UTC
  2. PowerBuilder
  3. # 2

The library files (.PBL) contain source code and executable code. When you save an object in the painter, it saves the source code and compiles the object to also update the executable code. This is why the 'Run Man' can run the application instantly.

The 'Full Rebuild' option recompiles every object in the Target or Workspace (depending on which one you chose). A full rebuild is only needed if major structural changes have been made to an object that is referred to by many other objects, an ancestor window for example.

The Project Deploy will create .EXE and .PBD files (.DLL for machine code). It is recommended that you do a full rebuild as part of the project deploy. When a .PBD is created, it just copies the existing executable code from the PBL to the PBD. It doesn't recompile any objects, that is why the Project has a Full or Incremental choice but not a choice of None.

The Incremental Rebuild only recompiles those objects that it determines had references to objects that changed since the last time they were compiled.

 

Comment
There are no comments made yet.
Steve Sagodi Accepted Answer Pending Moderation
  1. Monday, 15 April 2019 16:51 PM UTC
  2. PowerBuilder
  3. # 3

Hi, didn't quite answer the question "should you do a Full Build before executing a Deploy" ?

Steve

Comment
  1. Chris Pollach @Appeon
  2. Monday, 15 April 2019 16:58 PM UTC
Hi Steve;

In development, I typically do not - unless ... I have made major changes to ancestors or performed a "Get Latest" from my SCM. Then I always do a Full Build.

For production ... I always do ... including a PBL optimize beforehand.

Note: A Full Build might always be done as well on a Deploy depending on your Project's option settings.

HTH

Regards ... Chris
  1. Helpful
  1. David Peace (Powersoft)
  2. Wednesday, 17 April 2019 16:31 PM UTC
Hi

I'm with Chris, full build for production to be sure.



Cheers

David
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 15 April 2019 16:43 PM UTC
  2. PowerBuilder
  3. # 4

Hi Steve;

  A full build is basically forcing the IDE to run through & check the Object, Library, Target or Workspace aspects of your current application (depending on where you do a RHMB + Full Build).

  The Deploy option takes your current PBL or Target (again depending on where you use the RHMB) and created the P-Code / M-Code and EXE from you current application's PBLs. A Deploy from the project object defaults to the "target" it resides under.

HTH

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.