1. Robert Inzinger
  2. PowerServer 2020 or older (Obsolete)
  3. Monday, 2 September 2019 12:54 PM UTC

Hi

Is there any plan in the future to support .net standard (2.0) with powerbuilder c# integration?

Background: We have many ASP.Net Webservices and want to use Powerbuilder c# integration, but we don't want to migrate our ASP.Net Webservices to ASP.Net Core.

regards

Robert

Robert Inzinger Accepted Answer Pending Moderation
  1. Wednesday, 4 September 2019 05:53 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Why I am asking:

Our "legacy" software is a classical Client-server model and the business logic is written in Powerbuilder, C++ and C# (.net Framework). Years ago we began to switch to a web-based n-tier model by using ASP .Net webservice because it was the best way to reuse business logic (C++ and c#) from the old system. 

It would be nice to use our parts of the business logic that is written in Powerbuilder but  it is not so easy to switch from ASP .Net to ASP Net Core. If PowerBuilder's .NET DataStore  would be offerd as .net standard 2.0 we can use it.

Maybe .Net 5 will be the solution.

Regards 

Robert

 

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 4 September 2019 16:32 PM UTC
The .NET DataStore is compatible with .NET Standard 2.0 (https://www.nuget.org/packages/PowerBuilder.Data/). Only the Web API integration library requires ASP.NET Core (https://www.nuget.org/packages/PowerBuilder.Data.AspNetCore/), but I don't think you need the Web API integration library since you have you are creating ASP.NET Web services on your own.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 3 September 2019 18:26 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Robert,

Confused by your question or maybe I am misreading what you are saying?

Your ASP.NET Web services do not need to be migrated to .NET Core... PowerBuilder's HTTPClient/RESTClient can call any REST Web API no matter what underlying technology the Web service uses.  It doesn't even have to be .NET... you can call Java, Python, etc.

Now as far as if you want to create a new .NET web service using PowerBuilder's .NET DataStore object or use our automated C# migration solution to move some of your PowerScript business logic to C# Web APIs, then for those new Web services you create using .NET DataStore you will need to deploy that with .NET Core.

But even if you are doing new .NET Web services with .NET Core, you can still keep your old .NET Web services like they are and integrate them all into your project.  That's the beauty of the REST standard.

Regards,
Armeen

Comment
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 3 September 2019 00:43 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3
Hi Chris, et al,
I read Microsoft's direction for .NET as follows >>
Legacy .NET == "Full .NET framework"
Modern .NET == ".NET Core"
 
Current Legacy release is .NET Framework 4.8
Plan: No more major releases - .NET Framework 5.0 !
 
Coming Modern release is .NET Core 3.0
Plan:
Sep-2019 == .NET Core 3.0
Nov-2019 == .NET Core 3.1 (Long-term support)
Nov-2020 == .NET 5.0 
(marketing gimmick to drop Core and skip 4.0)
 
Plan to rename signals that Modern is future direction.
 
HTH /Michael
Comment
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Monday, 2 September 2019 20:33 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Hi Robert,

SnapObjects 1.0 (aka. C# for PB 2019) is based on .NET Core 2.1. This version supports .NET Standard 2.0.
Link: https://docs.microsoft.com/en-us/dotnet/standard/net-standard

Note: Link states that .NET 4.7.2 is required for full .NET Standard 2.0 support when using full .NET framework.

HTH /Michael

Comment
  1. Chris Pollach @Appeon
  2. Monday, 2 September 2019 20:46 PM UTC
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 2 September 2019 13:54 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 5

Hi Robert;

   The current plan moving forward is all via the .Net Core feature as far as I have heard. However, .Net 5 will change the entire landscape.

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.
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.