To start and use PowerServer Debugger successfully, be aware of the following important prerequisites and note:
-
PowerServer Debugger can work on both 32-bit and 64-bit machines. But for 64-bit machines, PowerServer Debugger can only work with 64-bit Internet Explorer.
-
PowerServer Debugger can work with Internet Explorer 9.0 or later (both 32-bit and 64-bit), and does not work with other Web browser such as IE 7/8, Edge, Chrome, Firefox, & Opera. However, you can run (not debug) the PowerServer Web application in the other Web browser.
-
PowerServer Mobile provides no debug tool, but you can still take advantage of PowerServer Debugger to debug the business logic of the mobile application in Internet Explorer.
-
Microsoft Script Debugger must have been correctly installed and registered on the same machine and script debugging is enabled in Internet Explorer. Otherwise, you may encounter problems in starting and using PowerServer Debugger.
-
Modify the Windows registration table: In order to make sure that the PowerServer Debugger work correctly, you need to modify the Windows registration table after the installation of the Microsoft script debugger.
For 64-bit machines, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\ in the Windows registry, add the following
-
one DWORD value: TabProcGrowth = 0
-
two String values: Isolation = PMIL, IsolationImmersive = PMIL
Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\, and if the same items exist there, make sure they have the same value as shown above.
For 32-bit machines, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\ in the Windows registry, add one DWORD value: TabProcGrowth = 0. Also go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\, and if TabProcGrowth exists there, make sure it is set to 0.
-
-
Enable the script debugging option: Simply uncheck the Disable script Debugging (Internet Explorer) checkbox under the Internet Options > Advanced tab in Internet Explorer.
If you encounter any error when starting the PowerServer Debugger, refer to the solutions in the section called “Appeon Debugger” in PowerServer Troubleshooting Guide.
-
-
A script in the deployed application must meet all of the following requirements to be debugged; otherwise PowerServer Debugger will simply ignore it:
-
The script is deployed in the Debug PS/JS or Debug JS mode using the local PowerServer Toolkit.
If you have changed the application PBLs, or the local application files and the remote application files are not the same, you must re-deploy the application. Or the newly-added code will not be selectable in PowerServer Debugger.
-
The original PowerScript code of the script is supported by PowerServer.
If the code is unsupported, it is marked with a
icon in the PowerServer Debugger
Source view, and cannot be set
as breakpoint, nor be located with the Run
To Cursor or Set Next
Statement commands in the debugger.
-
