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

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.

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

Steve

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