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

Resolved DLL Import

  1. How-to
0
Votes
Undo
  1. SHAMEEM KAKKAD
    SHAMEEM KAKKAD
  2. PowerBuilder
  3. Tuesday, 3 August 2021 04:08 AM UTC

Hai,

I created a simple .net dll in c# and imported to appeon. It is working perfectly. but in another system same dll imported and scripted. But I am getting this error.

---------------------------
PowerBuilder application execution error (R0058)
---------------------------
Application terminated.

Error: Object instance does not exist at line 8 in function of_name of object nvo_calculate.
---------------------------
OK
---------------------------

 

any system related issue ?

Application Versioning with automated builds
How to create a 64 bit EXE?
Responses (4)
SHAMEEM KAKKAD
SHAMEEM KAKKAD Accepted Answer Pending Moderation
  1. Friday, 6 August 2021 05:22 AM UTC
  2. PowerBuilder
  3. # 1

Anybody can help ?

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 3 August 2021 10:42 AM UTC
  2. PowerBuilder
  3. # 2

Are you using .Net Core for your DLL?

Make sure you have to correct 32 / 64 bit .Net Core Framework installed on "the other" system.

 

Comment
Load more comments
SHAMEEM KAKKAD
  1. SHAMEEM KAKKAD
  2. Wednesday, 4 August 2021 04:21 AM UTC
Using .Net framework
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Wednesday, 4 August 2021 08:19 AM UTC
So your pb app is also 64 bit?
  1. Helpful
SHAMEEM KAKKAD
  1. SHAMEEM KAKKAD
  2. Friday, 6 August 2021 05:00 AM UTC
Yes. 64 bit application
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 3 August 2021 10:27 AM UTC
  2. PowerBuilder
  3. # 3

Things I can think of:

1. If you're running powerbuilder 32 bit, make sure that your DLL hasn't been compiled as 64 bit.
2. Make sure your "is_assemblypath" is correct. If you use a "relative" path for it, then make sure that the "internal current directory" hasn't changed before you create the object. (by for example having read or written a file somewhere in a different folder than the application's directory, or having used GetFileSave/Open.. etc.).

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 3 August 2021 10:29 AM UTC
Also, make sure you don't put any debug stops withing the creation functions, I've seen it fail / hang many times when debugging through those functions.
  1. Helpful
SHAMEEM KAKKAD
  1. SHAMEEM KAKKAD
  2. Wednesday, 4 August 2021 04:00 AM UTC
No any debug stop within the function.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 3 August 2021 04:14 AM UTC
  2. PowerBuilder
  3. # 4

Did you deploy correct runtime DLLs to the other machine?  This .NET feature requires specific runtime DLLs: PBDotNet.dll, PBDotNetFrameworkInvoker.dll, PBDotNetCoreInvoker.dll 

Also, is the correct .NET framework version installed on the other machine?  

Comment
SHAMEEM KAKKAD
  1. SHAMEEM KAKKAD
  2. Tuesday, 3 August 2021 04:33 AM UTC
Regarding .net dlls

these dlls are available in the C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703



Framework



Microsoft .NET Framework 4.5 is already a part of this operating system. You do not need to install the .NET Framework 4.5 redistributable.



Any other problem ?
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 3 August 2021 04:47 AM UTC
Sorry, I don’t see any other obvious reasons why work on one machine but not the other.
  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.