Appeon announced on July 5, 2016 that it entered into an agreement with SAP to develop a new generation of the PowerBuilder development platform. Below are some answers to some common questions about the new generation of PowerBuilder. The official press release is available to view here.
We have scheduled to release new features of PowerBuilder for general availability in agile yearly cycles. For the foreseeable future, each product cycle will contain some level of enhancements to the core desktop projects. Maintenance releases will not contain new features and are scheduled for general availability on periodic quarterly cycles. Please review the product roadmap to understand the product release schedule.
The PowerBuilder IDE can be installed on Windows 7/8/10.
Desktop apps can be deployed to Windows 7/8/10 or Windows Server 2008/2012/2016.
Mobile Apps can be deployed to iOS 10/11 and Android 6/7.
The PowerServer Mobile (PB Edition) which provides runtime service to Mobile Apps requires Microsoft IIS 7.5 or newer.
The PowerBuilder IDE can be installed to 64-bit Windows OS but will run as a 32-bit process.
Desktop apps can be compiled to run as native 64-bit apps on Windows OS; however, if your app uses any third party DLLs you will need to provide 64-bit versions of those DLLs in order to run successfully as a native 64-bit app.
Mobile Apps can be compiled to run as native 64-bit apps on iOS; however, on Android currently only 32-bit apps are supported.
The PowerServer Mobile (PB Edition) which provides runtime service to mobile apps can run as a native 64-bit process utilizing the 64-bit version of the .NET framework.
You will be using the familiar and time-tested native PowerBuilder IDE, regardless you are developing traditional desktop apps, server-side .NET projects, or mobile apps.
The Visual Studio PowerBuilder IDE (PB.NET) has been discontinued, and is being replaced with a totally revamped approach to .NET using C# programming, open standards, and the native PowerBuilder IDE.
You will be scripting using PowerScript if you are developing traditional desktop apps or mobile apps. You will be scripting using C# if you are developing cloud apps. We recommend carefully studying the PowerBuilder roadmap to understand our plans.
Yes. Although PowerBuilder 2017 and 2017 R2 is based on the PowerBuilder 12.6 code base, Appeon removed the following features:
- PB.NET (Visual Studio IDE) & WPF Projects
- EAServer Projects/Targets
- Windows Form
- Web DataWindow
If you are using a version of PowerBuilder that is older than 12.6, please refer to SAP documentation about features that have been removed in previous versions.
.NET is a very important part of the PowerBuilder roadmap. Rather than make an incremental change to PB.NET, Appeon is investing to totally revamp PowerBuilder’s approach to .NET, its server-side architecture, and interoperability with open standards.
Beginning with PowerBuilder 2018, developers can leverage new targets to rapidly create RESTful Web APIs and non-visual .NET assemblies, in a test-driven manner, with the native PowerBuilder IDE and C#. Compared to PB.NET, these targets are 100% managed C# code and compatible with the .NET Core. OAuth 2.0 authentication is provided out-of-the-box. And you should notice a significant boost in performance and scalability.
|PowerServer Mobile (PB Edition)||PowerServer Mobile|
|Java Server Deployment||No||Yes|
|.NET Server Deployment||Yes||Yes|
|Co-exist with PowerServer Web||No||Yes|
|iOS Compatibility||iOS 11, 10||iOS 11, 10, 9|
|Android Compatibility||Android 7, 6||Android 7, 6, 5, 4|