Migrating existing projects under source control – PB Docs 2017

Migrating existing projects under source control

Migrating from earlier versions of
PowerBuilder

There are different strategies for migrating existing source
control projects from earlier versions of PowerBuilder. To migrate a
target from PowerBuilder 8 or later, you can check the target out from
source control, then add the target to a workspace in the new version
of PowerBuilder. When the Migrate Application dialog box prompts you
to migrate the libraries in the application library list, click OK to
begin the migration.

If you change the directory hierarchy for target libraries in
the new version of PowerBuilder, you should use the Existing
Application target wizard to create a new target instead of adding and
migrating a PowerBuilder 8 or later target. If you keep the old target
file (PBT) in the new target path, you must give the new target a
different name or the wizard will not be able to create a new
PBT.

For information on using the Existing Application target wizard,
see Using the Existing Application target
wizard
.

When you open a PowerBuilder 8 or later workspace in the current
version of PowerBuilder, a dialog box prompts you to migrate the
workspace targets. If you select the No Prompting check box and click
OK, the target libraries are migrated without additional prompting,
and the Migrate Application dialog box never displays. You can then
add the migrated target objects to source control from the new version
of PowerBuilder.

For more information about migration, see Migrating targets.

Removing PowerBuilder 8

If you remove PowerBuilder 8 from a computer where you have
already installed a later version of PowerBuilder, the setup program
deletes the PBNative registry entry. Subsequently, if you want to
use PBNative source control with PowerBuilder 2017 R3, you must
reregister PBNAT170.DLL. Attempting to use PBNative before
reregistering the DLL produces an error message that points out the
problem and the solution. You can reregister the DLL by opening a
DOS command box, changing to the AppeonSharedPowerBuilder
directory, and entering the command REGSVR32 PBNAT170.DLL.

Removing PowerBuilder 9 or later does not remove the DLL or
the registry entry for PBNative source control.

Migrating from PowerBuilder 7 or
earlier

Migrating an application from PowerBuilder 7 or earlier requires
a different approach, since workspaces and targets were introduced
with PowerBuilder 8. You need to create a new workspace and
appropriate targets for any PowerBuilder 7 (or older) objects that you
are migrating.

The strategies available to you or the project manager
are:

To use the first strategy, you must keep a copy of the old
version of PowerBuilder — at least until you have finished migrating
all your source-controlled PBLs.


Document get from Powerbuilder help
Thank you for watching.
Was this article helpful?
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x