A start rundown is triggered when logging under the rundown provider is enabled with the StartRundownKeyword keyword. This causes the DCStart event to be raised, and captures the state of the system. Before the start of the enumeration, the DCStartInit event is raised. At the end of the enumeration, the DCStartComplete event is raised to notify the controller that data collection terminated normally.
An end rundown is triggered when logging under the rundown provider is enabled with the EndRundownKeyword keyword. End rundown stops profiling on a process that continues to execute. The DCEnd events capture the state of the system when profiling is stopped.
Before the start of the enumeration, the DCEndInit event is raised. At the end of the enumeration, the DCEndComplete event is raised to notify the consumer that data collection terminated normally. Start rundown and end rundown are primarily used for managed symbol resolution. Start rundown can provide address range information for methods that were already JIT-compiled before the profiling session was started. End rundown can provide address range information for all methods that have been JIT-compiled when profiling is about to be turned off.
End rundown does not happen automatically when a profiling session is stopped. Instead, a tool that is seeking to perform managed symbol resolution has to explicitly invoke a CLR rundown provider session with the EndRundownKeyword keyword enabled, just before profiling is stopped.
Although either start rundown or end rundown can provide method address range information for managed symbol resolution, we recommend that you use the EndRundownKeyword keyword (which supplies DCEnd events) instead of the StartRundownKeyword keyword (which supplies DCStart events). Using StartRundownKeyword causes the rundown to happen during the profiling session, which may disturb the profiled scenario.
The following example demonstrates how to use the CLR rundown provider in a way that allows symbol resolution of managed processes with minimal impact, regardless of whether the processes start or end inside or outside the profiled window.
A tool can execute steps 2 and 3 (starting a rundown session and then terminating profiling) instead of immediately turning off profiling when a user requests profiling to be stopped. A tool can also execute step 4.
To the right of that, we have all the department columns. These columns can be renamed by double-clicking the header. These columns can also be hidden and re-ordered by any user in order to customize their rundown. hiding and re-ordering columns only apply to the user who made that change.
You can easily get started making changes to your rundown by simply double-clicking on a cell. This will bring you into edit mode and allow you to add/remove text and formatting. Simply clicking outside of the cell will exit edit mode and automatically save your changes.
If you want to apply formatting to an entire cell rather than specific text, the cell formatting toolbar can help you do just that. This toolbar appears near the top of your rundown whenever a cell is selected.
If your user has Showcaller permissions then you will see a blue "TRACK" button appear on any row you hover your cursor over. Clicking on that button will begin calling the show. This is the functionality you will use to let everyone know what part of the rundown is currently live. The Item Run Time clock is also tied to this functionality and the clock will reset whenever the Showcaller moves to the next row.
PDF exports are the best and most popular way of generating your rundown in an easy to print format. A PDF export will include all of your font formatting, highlight colors, and images in the common .PDF file format.
Guest Pass is a great way to share your event's rundowns, schedules, and lists with stakeholders who might not necessarily need their own Shoflo account. A guest pass will not have access to Showcaller Tracking or any real-time edits, but each refresh will fetch the latest version.
aa06259810