• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Consuming external .NET assemblies in .NET assembly target

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

Resolved Consuming external .NET assemblies in .NET assembly target

  1. Issue
0
Votes
Undo
  1. Arcady Abramov
    Arcady Abramov
  2. PowerBuilder
  3. Wednesday, 5 July 2017 12:35 PM UTC

Hello, all

I need to know what my options are in using external .NET assemblies in .NET assembly target of PB 2017.

I cannot find written help on that at all.

I see that I can import the assembly in the target and see them in the system tree. But how do I use the classes from this assembly? I used to work in PB.NET 12.5 and it was seamless there. Now I need to see what my options in PB 2017 are.

 

Thank you

Arcady Abramov

Silverbyte Systems

  1. Build
Using PB12.5 classic/PB2017 to send data to a webs...
ORCAScript and IDE shouldn't be run at same time
Responses (3)
Arcady Abramov
Arcady Abramov Accepted Answer Pending Moderation
  1. Wednesday, 5 July 2017 17:21 PM UTC
  2. PowerBuilder
  3. # 1

Hi, Chris

It is not really clear to me how the new version is supposed to work. In PB11.5 we had an option of using conditional code blocks. In PB12.5 we had the PB.NET.

Right now, I cannot figure out what I am supposed to do with an imported .NET assembly inside an .NET assembly target.

I see the imported assemblies, I see the classes, but how to get to them is a mistery. What's the point of using a COM wrapper on a target, which is going to be deployed as .NET assembly or service? 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 5 July 2017 15:18 PM UTC
  2. PowerBuilder
  3. # 2

PS: Also ...  http://pbdj.sys-con.com/node/1668463

 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 5 July 2017 15:14 PM UTC
  2. PowerBuilder
  3. # 3

Hi Arcady;

   Since PB 2017 is based on the PB Classic IDE - it can not consume a .Net Assembly in the same way as PB.Net could. In the case of PB 12.6 and now 2PB 2017 - you need to call a non-visual .Net assembly via (for example) the Windows PowerShell  or for a visual .Net assembly, make it COM Visible. 

  Appeon will be addressing these .NET compatibility issues as we move the product towards a fuller .Net interoperability in the next two releases.

Regards ... Chris

Comment
Arcady Abramov
  1. Arcady Abramov
  2. Wednesday, 5 July 2017 17:18 PM UTC
Hi, Chris



It is not really clear to me how the new version is supposed to work. In PB11.5 we had an option of using conditional code blocks. In PB12.5 we had the PB.NET.



Right now, I cannot figure out what I am supposed to do with an imported .NET assembly inside an .NET assembly target.



I see the imported assemblies, I see the classes, but how to get to them is a mistery. What's the point of using a COM wrapper on a target, which is going to be deployed as .NET assembly or service? 

  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.