Migrate Magic eDeveloper and uniPaaS to .NET by Upgrading
Reason #3: Checking and Debugging
Application maintainability is greatly enhanced through superior checking, debugging and error logging. Remember, in C# there is no official cross-platform runtime so any notion of being able to debug a cross-platform application within a single IDE is out-the-windows, forgive the pun. But even worse, and even if you just plan to deploy in windows only environments, you basically find yourself having to write a ton of code in order to debug your code.
Contrast that nightmare with Magic xpa where when you are in Debug mode, you can run a program in Runtime mode and the Debugger will park on the Studio read-only screen at the exact location of where you are in the program when a breakpoint is reached.
In the Magic xpa Debugger you can:
- View breakpoints and variable values within the task flow view. Breakpoints enable you to halt execution of the program at a specific location in the Studio screen.
- View the Magic xpa flow within the Studio using the Activity Monitor.
- Set conditions for the breakpoints.
- Create a Watch list that includes selected variables to be watched during runtime.
- Update variable values during deployment. When you update a value in the Debugger, you are prompted to confirm recomputation.
- View the flow from within the Studio.
- View the call stack.
- Switch between different contexts for debugging.
- Dynamically handle logs using the Logging function.
- Execute the Debugger remotely.
Checking and debugging requires extensive manual programming in C# and Java and misses out on the quality assurance features built into platform based computing approaches. For additional information on how an upgrade is superior to Magic to .NET conversion please convert here.
Glenn Johnson is a Senior Vice President at Magic Software Enterprises, Inc. Active in the software industry since 1984, he frequently speaks at industry conferences and writes for numerous publications.