The PowerBuilder ADO.NET interface supports the OLE DB, Microsoft SQL Server .NET, Oracle ODP.NET, and Sybase ASE data providers. If you use ADO.NET, you must deploy PBADO105.DLL, Sybase.PowerBuilder.Db.dll, Sybase.PowerBuilder.DbExt.dll, and, for OLE DB, the OLE DB data provider.
The file PBADO105.DLL is a standard DLL file, and you can deploy it in the same way as other PowerBuilder DLLs. However, Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll are .NET assemblies. You can use one of three techniques to deploy the files:
Deploy Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll in the same directory as the executable file that calls the ADO.NET driver.
Use a .NET application configuration file to assign the path of Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll. The file contains configuration settings that the common language runtime (CLR) reads as well as settings that the application reads. For an executable file, the configuration file has the same name as the executable file with the extension .config. The pb105.exe.config file in your PowerBuilder 10.5 directory is an example.
For more information about configuration files, see the Microsoft Visual Studio SDK documentation.
Add the Sybase.PowerBuilder.Db.dll and Sybase.PowerBuilder.DbExt.dll assemblies to the Global Assembly Cache (GAC). Use this technique only when an assembly must be shared by several applications. You can no longer install an application using xcopy if one of the assemblies it uses is in the GAC.
For more information about the GAC, see the section on the Global Assembly Cache in the Microsoft Visual Studio SDK documentation.
