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

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

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

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