Tuto WEBDEV 25

360 Part 10: Optimizing and debugging a project 5.  The report window of dynamic audit is displayed. ▶ Let’s study this window: • The top section of this window is used to choose the display mode of data. You can: • choose a chronological display (respecting the order in which the events occurred) or an overall display, used to group the different types of problems. During a chronological display, a chronological border allows you to see the position and importance of problems. • choose the type of problem to display (error, assertion, ...). This allows you for example to concentrate on the major errors, ... • The bottom section of this window displays the different events that occurred and that may cause problems in the application. ▶ In this example, the dynamic audit detects several problems: • A SWITCH statement for which no CASE is run, • A triggered assertion, • A triggered exception, • The assignment of a nonexistent image file to an Image control. For each problem, a "..." button is used to access the event details. If the event is linked to a specific line of code, the button allows you to open the code editor directly at the corresponding location in order to fix the problem. ▶ Close the window of dynamic audit. Remark The dynamic audit of a project can also be performed when the site is deployed. All you have to do is call dbgEnableAudit to trigger the dynamic audit. The audit generates a ".wdaudit" file, this file must be loaded in the development environment in order to study the result. See the online help for more details (keyword: "Dynamic audit").