When deploying your objects, you need to coordinate registry entries with the locations of all the files.
For both PowerBuilder.Application and a registered user object as a server, you need to deploy the PowerBuilder runtime environment on each user’s machine.
For information about PowerBuilder deployment and required files, see Part 9, “Deployment Techniques.”
Instead of the PowerBuilder executable, the registry looks for the PowerBuilder virtual machine DLL, PBVM105.DLL, to start the runtime environment. When you deploy, the path for this file is recorded in the registry. Users should not move the file to another directory—the registry entry would be made invalid.
The registry records the location of the library containing your object and the location of the type library.
Therefore, when you generate a registry update file on your own computer, path information reflects the file location on your machine. When you deploy, you can:
Customize the registry update file (it is an editable text file)
Make changes to the registry after it has been updated
You do this programmatically using functions in PowerBuilder or the Windows SDK, or manually with the Registry Editor.
