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

Resolved winform target upgrade

  1. Issue
0
Votes
Undo
  1. Bob Kelty
    Bob Kelty
  2. PowerBuilder
  3. Friday, 12 January 2024 19:19 PM UTC

I'm trying to upgrade a winform target from PowerBuilder 2019 R2 to PowerBuilder 2022 R3.  I get an error when trying to edit the project file: "Unable to open this project because the add-on software that was used to create it could not be found. Perhaps this project was built on another system".

Does anyone have any advice?

What is the most recent version of PowerBuilder that will compile a winform target?

Thank you,

Bob Kelty

University of Michigan

JSON problems inserting data into an array of an o...
Resizing issue in PB 2022 R3 (build 3289) when Tab...
Who is viewing this page
Joe Hess
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 12 January 2024 20:36 PM UTC
  2. PowerBuilder
  3. # 1

Hi Bob;

  FWIW: The "WinForm" project type deprecated a long time ago. The last PB version to support that Project type (I believe) was PB 12.5.2. Sybase & then next owner SAP removed both the Winform & WebForm Project types. So when Appeon took over PB from SAP these were no longer supported. I would just delete those old project types before you upgrade (migrate).  HTH

Regards .. Chris

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 15 January 2024 14:20 PM UTC
Hi Andreas;

These features were removed & deprecated. Just because it "somehow" got past the migration doesn't mean that they are supported by any Appeon PB version. So basically, a) we don't support them and b) you're basically "on your own".

Regards ... Chris
  1. Helpful
Andreas Mykonios
  1. Andreas Mykonios
  2. Monday, 15 January 2024 14:58 PM UTC
I haven't stated that they are supported. I stated that although they were deprecated the IDE will let you use them in some specific case. This should not happen...

Andreas.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 15 January 2024 17:43 PM UTC
I agree ... The migrator should block them or at least advise you to remove them as soon as your migrated target is ready to use. Also (IMHO) the "Migration Assistant" should flag it as well *before* you migrate.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 12 January 2024 19:29 PM UTC
  2. PowerBuilder
  3. # 2

Not understanding your question/issue because PowerBuilder 2019 R2 did NOT have a WinForm target.  WinForm target was discontinued after PowerBuilder 12.6.  

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 12 January 2024 20:32 PM UTC
I understand but WinForm target was discontinued after PB 12.6. So it should be expected it's not going to work in newer versions of PowerBuilder. The recommended migration path is to revert the project back to a classic PowerScript project and then migrate that forward.
  1. Helpful
Andreas Mykonios
  1. Andreas Mykonios
  2. Monday, 15 January 2024 09:19 AM UTC
Hi Armeen. I did also opened existing winform targets in PB 2017 & 2019 in the past. So what Bob says was possible (I haven't tried to do that recently).

Andreas.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 15 January 2024 22:34 PM UTC
Hi Andreas, Thanks for confirming, but no matter possible in past or not something since it is a "discontinued" feature should not be expected to continue working.
  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.