Abstract: Techniques are described herein that are capable of using a complex value-bearing language expression to generate metadata associated with an artifact. The artifact is configured to define a type and to further define the complex value-bearing language expression. The artifact is built from source code. The type defines functionality of the artifact. The complex value-bearing language expression describes a configuration of the artifact or of a function of the artifact. The functionality and the configuration are defined in the source code, are written in a same computer language, and are included in a same software project. A constant value is extracted from the complex value-bearing language expression at build time of the artifact by evaluating a syntax of the complex value-bearing language expression. During a build of the artifact, the metadata is generated to include the constant value.

Abstract: Systems and methods for sending in-product notifications to individual users of a software product or a specifically identified subset of users of the software product selected via their previously observed interactions with the software product.

Abstract: Systems and methods for sending in-product notifications to individual users of a software product or a specifically identified subset of users of the software product selected via their previously observed interactions with the software product.

Abstract: A diagnostic mechanism monitors execution of a user interface (UI) thread to detect execution of a long running task that may have caused the UI thread to become unresponsive. The execution time of the UI thread is monitored and when it exceeds a threshold, the UI thread's call stack is preserved to a mini-dump file. The completion time of the UI thread is also tracked and stored in a delay file. The mini-dump and delay files are then uploaded to a server where the collected data is aggregated overall execution runs by multiple users to identify the cause of the unresponsiveness.

Abstract: Embodiments allow a user to define event scenarios that are used to analyze callstack and context data. Scenarios that are delayed are flagged and reported to the user with an aggregated callstack of CPU samples taken during the delay. An aggregation is done for samples for the main user interface thread of the process that is being monitored. A user may select other threads to see the callstack aggregation for that thread. The user can identify which methods use the most time for a particular delay from the callstack presentation. An event analysis tool allows quick exploration of the responsiveness issues by visualizing delays as they happen and allowing the user to drill down into callstack details for selected delays.

Abstract: Embodiments allow a user to define event scenarios that are used to analyze callstack and context data. Scenarios that are delayed are flagged and reported to the user with an aggregated callstack of CPU samples taken during the delay. An aggregation is done for samples for the main user interface thread of the process that is being monitored. A user may select other threads to see the callstack aggregation for that thread. The user can identify which methods use the most time for a particular delay from the callstack presentation. An event analysis tool allows quick exploration of the responsiveness issues by visualizing delays as they happen and allowing the user to drill down into callstack details for selected delays.

Abstract: A diagnostic mechanism monitors execution of a user interface (UI) thread to detect execution of a long running task that may have caused the UI thread to become unresponsive. The execution time of the UI thread is monitored and when it exceeds a threshold, the UI thread's call stack is preserved to a mini-dump file. The completion time of the UI thread is also tracked and stored in a delay file. The mini-dump and delay files are then uploaded to a server where the collected data is aggregated overall execution runs by multiple users to identify the cause of the unresponsiveness.

Abstract: An immediate delay tracker tool listens for the occurrence of user-specified events that exceed a delay threshold. In an embodiment, the events are associated with immediate user actions processed by a user interface (UI) thread where the response time of the immediate user action requires an instantaneous response. When the event exceeds the delay threshold, the control flow of all the processes and/or threads in the system is recorded, filtered and then analyzed for the source of the delay.