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

Resolved Future of .NET Assembly target

  1. Misc
1
Votes
Undo
  1. Pascal Reinders
    Pascal Reinders
  2. PowerBuilder
  3. Thursday, 12 July 2018 10:29 AM UTC

Hello,

we’re going to begin using “.NET Assembly Targets” to bring some of our business logic to .NET (PB 2017 R2). Development should be kept up in PowerScript by now, so this way would provide us a good solution to use same code in both worlds simultaneously.

BUT in documentation regarding .NET Assembly target is says «…this feature is available and is still eligible for technical support, but will no longer be enhanced.»

In another post I read that the feature would be completely revamped.
(https://community.appeon.com/index.php/qna/q-a/pb-2017-net-assemblies-stable-feature)

 

So what about the future of “.NET Assembly target” and possible substitutions for porting NVO’s (that each access other NVO's, DataStores etc.) to .NET without rewriting all the code manually?
So will it be impossible to “convert” PowerScript (NVO) to .NET libraries on next versions?

Many thanks in advanced for clarification and BR,
Pascal

  1. .NET Assembly
  2. Target
PB2017 is crashing while migration from 12.5
Verify dw filter by PB
Accepted Answer
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 12 July 2018 22:06 PM UTC
  2. PowerBuilder
  3. # Permalink

There is no future for the current .NET assembly target and so Appeon doesn't recommend any customer begin a new project using those particular features.  Appeon is keeping those deprecated features in the product for backwards compatibility since some customers may not all be able to migrate off of it in time.

As Chris mentioned, what is replacing those deprecated features are new C# targets, that will be introduced in PB 2018, which is what we recommend customers use for new projects or going forward.  You can learn a little more about PB 2018 here: https://www.appeon.com/pb2018.html

If you'd like to sign up to be a beta tester, please send an email to support@appeon.com with your request.  If approved, we would contact you around November with the beta version of the C# features.

Comment
There are no comments made yet.
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 12 July 2018 14:08 PM UTC
  2. PowerBuilder
  3. # 1

Hi Pascal;

  Yes, there will be a new .NET Assembly feature coming in PB2018. This new Assembly feature will be based on the latest .NET technologies and you will be coding in pure C# right within the PB2018 IDE (which will now have the "Roslyn" compiler embedded).

  The current .Net Assembly feature that uses the PowerScript language will continue "as is" for the time being.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Pascal Reinders
Pascal Reinders Accepted Answer Pending Moderation
  1. Friday, 13 July 2018 06:36 AM UTC
  2. PowerBuilder
  3. # 2

Hello Mr. Mazda,

thanks for your quickly reply - I think we will try to subscribe for beta tester to get a better idea of our future possibities.

Is it possible to give a little more detail to the "NVO Migration" feature in 2018 before?
(see https://www.appeon.com/developers/roadmap/pb-nvoeaserver-nvo-migration.html)

In the blog it talks about "refactoring" existing Powerscript, but is it also planned to give some real PowerScript -> C# migration assistance for 2018 version?

Many thanks again,

Pascal

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 13 July 2018 09:55 AM UTC
The refactoring tool is focused on helping to partition out useful business logic. It's not going to take an existing PowerScript NVO and convert it to exact equivalent and functioning C# NVO. If you have existing PowerScript NVOs you want to convert to C# then manual work will be involved, but with DataWindow migration and the server-side C# framework PowerBuilder provides it's going to be a small fraction of the coding effort compared to rewriting in C# with another tool (e.g. Visual Studio) and another server-side framework (e.g. Entity Framework). Please take a look at some of the code samples here: http://showcase.appeon.com
  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.