You may encounter the following known issues in this release. We are working diligently to resolve them in the coming releases.
PowerBuilder 2022 R3 Build 3382 has the following known issues:
-
After you enable TabbedView for an MDI window, PowerBuilder will automatically add a TabbedBar control to the window and allow you to access some properties. However, the TabbedBar control can only be used to implement the TabbedView feature in the current version. Please do not add the TabbedBar control manually or call its function/event/property, except the properties listed in Displaying sheets in tabbed view.
-
When TabbedView is enabled, maximizing or shrinking the MDI frame window will only cause the active sheet (initially opened at the maximized state) to maximize or shrink, the other sheets will not. For example, if the MDI frame window is opened (NOT at the maximized state) and then sheets are opened at the maximized state, and if the MDI frame window is maximized manually, only the active sheet will be maximized, the other opened sheets will not. And similarly, if the MDI frame window is opened at the maximized state and then sheets are opened at the maximized state initially, if the MDI frame window is shrunk manually, only the active sheet will be shrunk, the other opened sheets will not.
-
If the URL of PowerBuilder/InfoMaker Installer is launched within the MS Office (such as Outlook, Word, Excel, etc.), Windows SmartScreen will display a warning before downloading the installer via the Web browser: "XXX could harm your device. Do you want to keep it anyway?" XXX could be any executable file that SmartScreen considers as not well-known or not many downloads. This is normal protection behavior of Windows SmartScreen. You can click Keep to continue; or open another Web browser and then launch the URL of PowerBuilder/InfoMaker Installer from there (to avoid the warning).
-
When using PBAutoBuild to deploy an application, it takes longer than when using PowerBuilder IDE. This is an expected behavior. PBAutoBuild can be used freely outside PowerBuilder IDE. It has different compilation logic and uses different compilation methods. Moreover, it has more internal detections and error correction functions than PowerBuilder IDE, which cause differences in performance. For example, using OrcaScript to import objects to PBL fails while using PBAutoBuild Merge can succeed. If the PowerBuilder application is small, for example, the Sales demo, then the performance of PBAutoBuild is close to that of PowerBuilder IDE, but if it is a large and complex application, the performance of PBAutoBuild is much slower than PowerBuilder IDE, possibly 50% or more.
PowerServer 2022 R3 Build 3382 has the following known issues:
-
If the user wants to edit a ".NET 8" PowerServer Web API solution (such as configuring the auth template), due to the fact that SnapDevelop does not support .NET 8, the user has to use an external C# IDE that supports .NET 8, such as Visual Studio.
The following are not bugs, but 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.
