1. Roland Smith
  2. Beta Testing
  3. Tuesday, 22 September 2020 13:59 PM UTC

What will happen when the next major version comes out?

Will PB190.EXE only work with 2019 builds?

Will there be a PB210.EXE for PB 2021 (assuming that is the next major)?

 

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 22 September 2020 14:22 PM UTC
  2. Beta Testing
  3. # 1

Yes, that is basically the idea.  The table in the document explains in more detail: https://docs.appeon.com/pb2019r3/whats_new/Separating_Runtime_from_IDE.html

So before we did this enhancement to the design of the IDE, the revision number of the IDE and runtime had to match (e.g. PB 2021 R2 IDE could not deploy to PB 2021 runtime).  Now, a newer IDE can deploy to all previous revisions and even previous build numbers of runtime.  The only dependency is the major version of the runtime and IDE need to match (e.g. 2021), but we may be able to improve that in the future.

 

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 22 September 2020 23:03 PM UTC
The other main reason (maybe even the #1) for splitting the run-time was in the support of the new PowerClient (PC) feature. Now that the RT is separated, PC can control the deployment & update of the RT(s) on the remote client PC's. ;-)
  1. Helpful
  1. Ricardo Jasso
  2. Wednesday, 23 September 2020 00:55 AM UTC
What I suppose this will also mean is that if I start using new features from say PB 2021 R2 IDE / Runtime and then change the Runtime in the System Options to PB 2021 GA I will start getting error messages when performing an incremental or full build. It's like having different framework versions available to develop and compile, I guess.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Wednesday, 23 September 2020 01:22 AM UTC
Yes, a newer feature would not compile correctly if you target an older framework.
  1. Helpful
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.