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

Resolved PB17 - builds need full install of Appeon or no?

  1. How-to
0
Votes
Undo
  1. JOHN THOMAS
    JOHN THOMAS
  2. PowerBuilder
  3. Tuesday, 26 February 2019 22:05 PM UTC

Folks - we are trying to do our first build releases under the new Appeon PB17 and need some feedback on runtime environment.  With the old SAP/Sybase PB12, we were, I'm pretty sure, able to put  exe + pbd's in a folder, and just plop all the PB runtime dll's into the folder with the build and the exe would run (provided db connections and everything were ok via ini file, etc), whether a PB IDE install was on the box or not.

From trying this sort of operation with the new Appeon PB, it is looking more and more like the full PB IDE install needs to be done (including resulting registry entries), for any build to run on that box. Can anyone confirm/deny this is the case? We are trying to avoid having to set up the IDE in every prod box we're distributing to, if possible. A list of minimal runtime dll's to allow a build to run would be very nice, if there's a link to it on the site here or whatever. 

thanks much!

jt

 

 

-----

update 3/5

All - pretty much have the situation solved, I used the Runtime Packager to make an .msi file and it filled the bill except for one thing, see attached Word doc with shots, etc. I'm wondering if or how I can get the packager to bundle the addl ATL100.dll in with all the other files, it is the only one missing that our apps (an other people's?) needs.  Thanks!

Attachments (1)
Packager runtime files vs IDE runtimes.pdf
  1. IDE
  2. Installation
  3. Runtime Packager
PowerBuilder Security Code Scanning
Changing a protect property on a specific row in a...
Responses (4)
JOHN THOMAS
JOHN THOMAS Accepted Answer Pending Moderation
  1. Wednesday, 27 February 2019 19:40 PM UTC
  2. PowerBuilder
  3. # 1

Thank you all! Very helpful.

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Wednesday, 27 February 2019 15:22 PM UTC
  2. PowerBuilder
  3. # 2

link to *some* of the runtime files:

https://www.appeon.com/support/documents/appeon_online_help/pb2017r2/application_techniques/ch33s04.html

 

you have to look at some other pages in help to find some of the optional runtime files, plus the ones specific to your database.

search in help under "deploy an application"

 

 

 

 

 

Comment
mike S
  1. mike S
  2. Wednesday, 27 February 2019 15:25 PM UTC
also, the above is apparently the R2 release runtime list. So you need to check which version YOU are deploying and adjust as required. I do believe R2 and/or R1 had one weird dll that was was required, and is no longer required in R3.
  1. Helpful
There are no comments made yet.
Eric Freudenberg
Eric Freudenberg Accepted Answer Pending Moderation
  1. Wednesday, 27 February 2019 07:14 AM UTC
  2. PowerBuilder
  3. # 3

Hi John,

in our company we use two ways, both works fine. You must choose which is the better solution for your software.
1. Install the PB17 Deployment-Kit and refer via the registry to the install-location. So you must not copy the runtime files in your app folder and other PB17-Apps with the same runtime version can use the runtime.

2. (our preferred way) We copy the pure runtime files in a subfolder of the installation of our app, then refer via the registry to this folder. Note: for this way you must register some runtime files via regsvr32.exe or regasm.exe (GAC). In case 1 the Appeon Runtime Installer takes over this part. See this thread for more informations: https://community.appeon.com/index.php/qna/q-a/using-different-runtime-kit-releases-simultanly-gleichzeitige-verwendung-verschiedener-runtime-kit-releases

Comment
There are no comments made yet.
Andrew Barnes
Andrew Barnes Accepted Answer Pending Moderation
  1. Tuesday, 26 February 2019 22:29 PM UTC
  2. PowerBuilder
  3. # 4

PB2017 deployment is more or less the same as PB12.5 deployment, just deploying the nnnnn170.dlls where you had deployed nnnnn125.dlls previously.  Last year, we upgraded our code base from PB12.5 to PB2017 and experienced no deployment issues.

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.