Changes
/* A general policy for debugging */
## If this didn't help, we need to look ourselves.
## Try to visualize what steps the algorithm goes through in the code
## Create a working hypothesis what' going on: "I think what's going on is... !"
## Find a good entry point for debugging in the code
## Attach the debugger of an IDE (like Visual Studio) to the process if possible
This is basically independent of the product or framework you're using. With {{UBIK}}, we can get more concrete.
[[Category:Best Practices (internal)|Debug a Customizing]]
[[Category:Resources (internal)|Debug a Customizing]]
== Debugging {{UBIK}} ==
