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

Resolved future webassembly deployment instead of appeon plugin?

  1. Advice
1
Votes
Undo
  1. Michael Kench
    Michael Kench
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 16 November 2018 01:08 AM UTC

Hi guys,

I am hearing a bit of buzz around browser support for webassembly and wondering if this is something appeon may be looking into for future powerbuilder web deployment. The appeon plug-in is the reason we have not used Appeon Web for any of our web portals.

Michael

Powerserver Maximum Universal Sessions & Devices
of_logonfileserver doesn´t work
Responses (4)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 16 November 2018 01:46 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

PowerBuilder 2018 introduces C# server-side development (Web APIs and assemblies), and PowerBuilder 2018 R2 is scheduled to add ASP.NET development capability.  There is also plans for the next major version (e.g. PowerBuilder 2021) to introduce a Desktop Cloud App, which is basically the current native PB client but Internet friendly (installs and updates over the Internet with incremental updating).  You may also want to try the IWA (installable web app) option of PowerServer to see if that resolves your concerns about the browser plug-in if you are looking for the least-effort approach to the cloud.  I would recommend you watch the recordings of the keynotes from the Elevate 2018 conference: https://elevate.appeon.com

 

Comment
Michael Kench
  1. Michael Kench
  2. Friday, 16 November 2018 05:41 AM UTC
Thanks.

I'd be interested to hear more about the ASP.NET development capability scheduled for 2018R2. Any chance of a modernized version of the webdatawindow running in asp.net.

I couldn't see any new recording for Elevate 2018. I will check out the recordings when they become available.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 16 November 2018 05:54 AM UTC
The ASP.NET development does not have any value-added features. So there would be no DW controls in the page, and you may want to look at controls from Telerik or DevExpress to bind to the C# assemblies you create with PowerBuilder. The area we are adding value is the development of C# business objects (Web APIs or assemblies) as well as the new Desktop Cloud App (client side is scripted in PowerScript).
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 13 January 2020 17:52 PM UTC
FWIW: Michael - What Armeen is talking about is PB2019R2 and then into PB2019R3. There is no PB2018

  1. Helpful
There are no comments made yet.
Gzim Ramizi
Gzim Ramizi Accepted Answer Pending Moderation
  1. Monday, 13 January 2020 12:45 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Dear Armeen,

 

since the recommendation of W3C for WebAssembly this topic becomes more relevant. Are there new/any intentions to move PowerBuilder/DataWindow in this direction?

 

Kind Regards,

gzim

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 14 January 2020 01:15 AM UTC
Hi Gzim,

For PowerServer we are researching ways to run it as a desktop cloud app. It would not be pure HTML, but it would be an Internet-connected app that has an Internet installer and auto-updates. Compared to current PowerServer, it would basically have almost no unsupported features, require very little effort to convert, and offer better performance.

For DataWindow specifically, we plan to create an HTML5 DataWindow control that is separate from PowerServer. So for customers that are willing to do more conversion work they can go to HTML. PowerServer would be the almost-no-effort solution for customers that don't have mandatory requirement for HTML.

Regards,

Armeen
  1. Helpful
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 14 January 2020 17:01 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Michael,

As I write this reply the intro session of "Focus on Blazor" (today's .NET Conf event) where Microsoft discusses status of .NET and WebAssembly is winding down.

As I understand the presentation: Support for WebAssembly is part of coming "Blazor WebAssembly". This is scheduled to reach its FIRST LTS version by NOVEMBER 2021.

So Appeon's plug-in would have to be 100% rewritten in Blazor to have support from .NET. So earliest long-term support from Microsoft on WebAssembly as a deployment platform is late 2021. I'm neither Appeon employee nor product manager, but I myself would not commit to supporting WebAssembly as platform for my .NET initiatives until Microsoft delivers first long-term support version of such platform.

I fully agree Appeon should look at what happens regarding .NET and WebAssembly. I'm sure they do. However, I don't see product releases for "safe production environments" happening until late 2021 or even later.

Just my two Euro-cents, /Michael (another Mick)

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 14 January 2020 17:29 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

A recent study found that 50% of websites using WebAssembly are using it for malicious purposes.

https://www.infoq.com/news/2019/10/WebAssembly-wasm-malicious-usage/

 

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.