You need to deploy several types of files with a Windows application:
After you build a Windows form .NET application, you need to deploy the executable file and any DLLs that were compiled and saved in the Release\bin directory on the development computer. The files should be installed in the application’s directory on the target computer.
The deployment library (PBD) or PBL file or files that contain the DataWindow objects used in your application need to be distributed with your application in a directory on the system path. At runtime, the DataWindow server strips the full path from each library and looks for the library in the system path. If you have more than one copy of a library, one in the path specified in the library list and one in the system path, you might see unexpected results when you run or debug the application if the DataWindow exists in only one version of the library or has been modified in only one version.
For information about PBDs, see “About deployment libraries”.
You must deploy a set of core DataWindow .NET runtime files with a DataWindow .NET application, as well as files that are required if your application uses specific features. The application looks for the files in the directories in the same directory as the executable file or in the system PATH environment variable. For a complete list of files, see “DataWindow .NET runtime files”.
Some of the files you need to deploy, DataWindow.dll, DataWindowInterop.dll, Sybase.PowerBuilder.Db.dll, and Sybase.PowerBuilder.DbExt.dll, are strong-named assemblies. A strong name includes the assembly’s identity as well as a public key and a digital signature. The way you deploy these files can limit your choice of deployment techniques. For more information, see “Deploying .NET assemblies”.
