You may encounter the following known issues in this release. We are working diligently to resolve them in the coming releases.
Migration Assistant and WebBrowser:
-
The engine for the WebBrowser control is changed from Chromium Embedded Framework (CEF) to Microsoft Edge WebView2. The current Migration Assistant cannot report the changes occurred during WebBrowser engine upgrade, including changes to the existing functions and events, changes to the distribution modes, runtime files, etc.
For detailed instructions on migrating the WebBrowser control, refer to WebBrowser engine changes.
WebBrowser:
-
Executing SetRedraw on the front MDI sheet will cause the WebBrowser control on the back MDI sheet to flicker.
SMTPClient
-
The SMTPClient Support option in the PowerBuilder Runtime Packager will only package pbsmtpclient.dll and libcurl8_0_1.dll, but will not package libcurl.dll. You will need to manually copy libcurl.dll from the runtime folder (e.g. C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.1.0.2819) if your application uses SMTPClient.
ADO.NET Connection:
-
In the database painter > ADO.NET database connection, right click a table and select Alter Table, the default value is currently unsupported.
-
In the database painter > ADO.NET database connection, right click a table (or view) and then select Print Definition, the exported PDF file will have no database name.
-
If the Outer Join Syntax in the ADO.DB profile setup is set to PB in the database Profiles > ADO.NET, there may be "column not found" error reported on DataWindow syntax.
-
It is unsupported to set a custom Identifier Quote Character in the database Profiles > ADO.NET. The default character (") is always used.
-
It is unsupported to use the ADO.NET connection if the IDE switches to use a lower PowerBuilder Runtime.
-
The ADO.NET connection will return a hexadecimal data when converting a binary data to a string. For example, supposing the original value is a blob ('haha'), ADO.NET connection returns 0x*****, while direct connection returns "haha".
-
When an ADO.NET data type do not match the one in the Select Into or Fetch statements, the program will make a forced conversion, which may cause loss of data.
-
If you modify a Date or TimeStamp value in a table under the ADO.NET for Oracle connection, an error occurs when saving the change.
-
The default value for parameter of Oracle stored procedure is unsupported. When calling a stored procedure, if the parameter has a default value, the execution will fail.
-
When querying data from an ASE database via ADO .NET ODBC, if the return value is bigtime or time data type, the millisecond portion will be missing.
.NET DLL Importer:
-
If dotnetcoreversion is not specified when calling LoadWithDotNetCore, an error code -20 will return. It is recommended to use LoadWithDotNet.
PowerBuilder Runtime Switching:
-
After upgrading to PowerBuilder Runtime 2022 R2, if you switch back to PowerBuilder Runtime 2022 GA, there may be "incorrect syntax" error at regenerating or building DataWindows. The reason is that there are new properties added to DataWindows in 2022 R2. If you want to continue working in 2022 GA, please either open the DataWindows and save, or manually remove the following code lines in the DataWindow Edit Source: data.export.format; dddw.autocompletemode; ddlb.autocompletemode.
RichTextEdit:
-
In the 64-bit application, if the textPos argument of TableInsert is set to a value that is not -1, the Insert Table dialog box will be displayed, and the textPos argument will have no effect. (There is no such issue in the 32-bit app). To workaround this issue and avoid the dialog box in the 64-bit app, you can consider using the following scripts:
long ll_row,ll_col,ll_textPos rte_1.SelectedStartPos = ll_textPos rte_1.SelectedTextLength = 0 rte_1.TableInsert(ll_row,ll_col,-1)
PowerServer 2022 R2 GA has the following known issues:
-
If you change the Web API target framework back and forth for PowerServer deployments, it is recommended to clear up the cache or the files on the IIS server before deploying. Otherwise, it is possible that the PowerServer Web APIs may fail to start.
-
The CustomizeDeploy.dll tool cannot change external files. Please download this hotfix and replace the old CustomizeDeploy.dll if you want to use this tool.
The following are not bugs, but useful tips to help you use PowerServer easily and successfully:
-
If you plan to deploy a PowerServer project to External > IIS server, it is important to follow the PowerServer Help to prepare the IIS server (local or remote), especially, downloading and installing the ASP.NET Core hosting bundle on the server. A very common cause for the application to fail to run (with an HTTP error such as "http 500.19 error") is that the hosting bundle is not installed on IIS.
-
It would take unusual long for the IDE to deploy a PowerServer project for the first time (the deployment process will download the necessary .NET Core libraries). Then the subsequent PowerServer project deployments will return to the normal speed. This is normal behavior.
