Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Migrating PB-2017 to PB-2022

  1. How-to
0
Votes
Undo
  1. Michael McGraw
    Michael McGraw
  2. PowerBuilder
  3. Wednesday, 28 February 2024 18:15 PM UTC

Environment. Converting Powerbuilder 2017 to Powerbuilder 2022

Is there any way to bypass the C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.2.0.3289 access/process and be able to use an in house directory for processing the DLLs, both PB and Custom?

I've been checking into using the App Paths, but haven't figured out how that would work with our application.

We really need to keep the custom directory to avoid major changes to our distribution process.

Regards,

Mike McGraw

Sequence syntax from Oracle to SqlServer
How safe is the /LARGEADDRESSAWARE flag for 32-bit...
Responses (1)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 28 February 2024 18:56 PM UTC
  2. PowerBuilder
  3. # 1

When you deploy the executable, an .xml file is created which contains the folder where the runtime folder is located. You just need to deploy the file with the exe. You can modify the path in the .xml file to where the runtime is located.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.