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

Resolved Compiling .NET assebly in PB

  1. How-to
0
Votes
Undo
  1. Daniel Oralek
    Daniel Oralek
  2. PowerBuilder
  3. Wednesday, 26 February 2020 09:15 AM UTC

Hi, I am looking for possibility to automaticaly compile .net assebly. I found only way do it is direct in PB enviroment. How can I do by PBC190 or by orcascript?

 

Best regards

dao

changing buttons look style
close an external application with Powerbuilder ?
Responses (3)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 26 February 2020 17:10 PM UTC
  2. PowerBuilder
  3. # 1

Hi Daniel,

As Arnd pointed out, this is an obsolete feature.  Appeon strongly recommends that you make plans to move off of obsolete features since they are not going to be enhanced or get technical support/fixes. 

But the bigger issue you are eventually going to face is you won't be able to upgrade to newer versions of the .NET framework because Microsoft is replacing .NET with .NET Core starting with the next version of .NET.

To move off of this particular obsolete feature, we recommend you use the PowerScript Migrator to migrate your assemblies to C# and .NET Core, then compile with the SnapDevelop IDE included with PowerBuilder.

Regards,
Armeen

Comment
There are no comments made yet.
Daniel Oralek
Daniel Oralek Accepted Answer Pending Moderation
  1. Wednesday, 26 February 2020 11:02 AM UTC
  2. PowerBuilder
  3. # 2

Ok. I know about using IDE with command-line arguments. But I am looking for a way to use it on computer which is dedicated for compiling our projects.

Comment
Michael Kramer
  1. Michael Kramer
  2. Wednesday, 26 February 2020 11:22 AM UTC
That target type being "stable"/"obsolete", I see no changes going forward.
  1. Helpful
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Wednesday, 26 February 2020 09:37 AM UTC
  2. PowerBuilder
  3. # 3

Hey Daniel, to understand correctly: You have a PB target to create a .NET assembly from a PB NVO. That target has a project object defining how to generate its .EXE - and you want to invoke that .EXE generation from command-line script so you can automate it. Correct?

In any case: Such target is a ".NET" target (read: PB-to-.NET) not a "PowerBuilder" target (read: "PB PowerScript"). ORCAScript was created long before .NET targets were introduced - and I believe it was never extended to cover targets beyond PB PowerScript targets.

PBC command-line compiler created by Appeon supports PB PowerScript targets only.

HOWEVER, scriptable compilation is still possible using IDE with command-line arguments. See:

  • PowerBuilder Help
    • Users Guide
      • The PowerBuilder Environment
        • Working with PowerBuilder
          • Building workspaces
            • From a command line

HTH /Michael

Comment
Load more comments
Arnd Schmidt
  1. Arnd Schmidt
  2. Wednesday, 26 February 2020 11:01 AM UTC
PBC was created before .NET targets were declared obsolete.
  1. Helpful
Michael Kramer
  1. Michael Kramer
  2. Wednesday, 26 February 2020 11:20 AM UTC
Also, true.

Appeon knew its forward direction, I guess ;-) - - and PBC started with focus on majority of cases = PowerScript apps.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 26 February 2020 16:25 PM UTC
Michael's guess is exactly right. Appeon could not EOL such a core feature that had gotten adoption until we had a replacement, which came in PB 2019.

  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.