1. Mike Kolenda
  2. PowerServer
  3. Wednesday, 2 August 2023 16:00 PM UTC

We are working on migrating our PowerBuilder code to utilize PowerServer 2022 and we've identified that most of the methods/objects in Appeon_Workarounds.pbl no longer work.  One of these is the  AppeonDotNetComponent.

We utilize the AppeonDotNetComponent to communicate with a variety of methods contained in .NET DLLs.  Looking for resolutions, we came upon "Calling .NET Assembly" and the  .NET DLL Importer tool.

1. Are there any other alternatives to comunicate with .NET DLLs in PowerServer 2022?

2. Has Appeon provided any publications to assist in converting features used in Appeon_Workarounds.pbl when migrating to PowerServer 2022. I have yet to find this resource if it is available.

Any guidance would be greatly appreciated.

Regards, 

Mike

 

Mike Kolenda Accepted Answer Pending Moderation
  1. Monday, 11 September 2023 17:46 PM UTC
  2. PowerServer
  3. # 1

I appreciate the feedback, gentlemen.

We have become rather reliant on the contents of the Appeon_Workarounds.pbl provided over 10 years ago. We are assess our migration from PB 2019 to PB 2022 R2 and thought there might be a roadmap available to chart that course.

We're busily working to convert our existing code to utilize REST API.

Thanks for the insight!

Regards, 

Mike

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 2 August 2023 17:19 PM UTC
  2. PowerServer
  3. # 2

What Roland said is exactly right.  You can now do this natively in latest versions of PowerBuilder or PowerServer so no need for a "workaround". Alternatively, if you expose the .NET DLL as a REST API you can call it from latest versions of PowerBuilder or PowerServer using the HTTPClient: https://docs.appeon.com/pb2022r2/objects_and_controls/HTTPClient_object.html

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 2 August 2023 17:01 PM UTC
  2. PowerServer
  3. # 3

PB 2019-R2 and higher can make .Net calls directly using the DotNetAssembly and DotNetObject objects. The IDE has a wizard to create a wrapper PB object that you can use if you want, not required.

Our desktop app had a need to connect to a .Net library and was PB 2019 GA at the time. I coded a wrapper DLL in C# to make the function argument datatypes be PB compliant and used OLEObject to connect.

 

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 2 August 2023 16:59 PM UTC
  2. PowerServer
  3. # 4

Hi Mike;

  The Workarounds library was for Appeon Mobile & Appeon Web products that were last supported in PowerServer 2020. PS2021 & higher is based on a totally new technology (Cloud computing). Thus, the Workarounds library is totally deprecated & removed. You cannot use that library or its features any longer with PS2021/2022.

Regards .... Chris 

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.