Exporting the Runtime Visualization

The graphical runtime visualization can be exported to the following formats:

• Portable Document Format (.pdf) file for later viewing and printing.
• Delimited text file (.csv)
• Visio® XML diagram (.vsdx) file for later use in Microsoft Visio®.
• Portable Network Graphic format (.png) for later viewing.
• JPEG format (.jpg) for later viewing.

Option 1  To export the runtime visualization

1. Use Runtime Visualizer functions to tailor the content of the runtime visualization before exporting. For more information, see Working-with-Runtime-Visualizer.
2. Right-click and select Export, or press Ctrl+Alt+E. The Export Visualization dialog box appears.
3. Select the desired export file format from the Format list.
4. Click Browse and browse to the desired location for the exported visualization.
5. If Export Image (PNG, JPEG) was chosen from the Format list, select *.png or *.jpg from the Save as type drop-down list.
6. Enter a file name for the exported visualization and click Save.
7. If exporting to a delimited text file (.csv), go to step 12.
8. To optionally include a title for the exported visualization, type the desired title in the Title field.
9. To optionally include the current date, select the Include date check box.
10. To optionally include a watermark, select the Include watermark check box.
11. To open the saved file automatically after export, select the View document after export check box.
12. Click Finish. If a file with the specified name already exists, a prompt will appear to confirm overwriting the existing file. The file is generated and -- if the View document after export check box was selected -- opened in your system's default viewing application for the exported file type.

For more information, see Exporting-the-Runtime-Visualizer-Events-Views-and-Call-Stack-Text-View.

Option 2 Automating CSV generation in Code Debug prespective

1. In the launch configuration, select the Export checkbox.
2. Provide the desired file path where the CSV should be saved.
3. Start the debug process as usual.
4. Once the debug session terminates, the data from the table will be automatically exported to the specified CSV file.

This setup streamlines the post-debug workflow by eliminating manual data extraction and ensuring consistent output.