In addition to
.NET modules or assemblies, PowerBuilder can generate PBD files
for application PBLs containing DataWindow, Query, or Pipeline objects.

Pipeline objects are supported in Windows Forms targets, but are not currently
supported in the .NET component targets. The PBD files
are linked as external resources with the generated .NET modules and assemblies.

If you use incremental builds for your Windows Forms,
the PBD files are generated only for selected PBLs in which modifications have been made
to DataWindow, Query, or Pipeline objects. For these target types, the PBD files are
generated in a �pbd� subdirectory of the TargetName.pbt_build directory. The PBD files are deployed together with the
generated .NET modules or assemblies. On deployment, they are not deleted from this
subdirectory since they are used to check for changes during subsequent incremental
builds.

If you use full builds, PBD files are always generated for
selected PBLs containing DataWindow, Query, or Pipeline objects
even when there are no changes to these objects�although
you can prevent generation by clearing the check box next to the
PBL name on the Library Files tab page of the Project painter. Since
you cannot use incremental builds with .NET component targets, PBD
files are always generated by default for these target types.