.NET Debugger Restrictions
The .NET debugger supports most features of the debugger for
standard PowerBuilder applications, including expression evaluation
and conditional breakpoints.
It does not support the Objects in
Memory view or variable breakpoints, which are not supported in
.NET. Local variables that are declared but not used do not appear
in the Local Variables view in .NET targets.
- Single-stepping between events � in the .NET debugger, when you step into a statement or function
in an event script, the debugger shows the next line of code.
However, if you step into a different event script, the debugger
continues execution to the next breakpoint. Add a breakpoint
to each event that you want to debug.For example, if you have set a breakpoint in the application’s
Open event, and the script opens a window, the debugger does not
step into the window’s Open event. You should set a breakpoint in
the window’s Open event or in a user-defined event that is called
from the Open event. - Setting breakpoints in modified code � if you modify your code after successfully debugging a .NET
application, you must redeploy the application before you debug
it again. Although you can still set breakpoints in modified lines
of code before you redeploy an application, the debugger debugs
only the last deployed version of your application. - Remote debugging � debugging of
Web
Service targets is not supported for applications
or components deployed to remote IIS servers.
For information about standard PowerBuilder debugger features,
see Users
Guide > Debugging an application.