Developers can run diagnostics tooling on their iOS and Android devices #46371
Labels
area-Meta
os-android
os-ios
Apple iOS
Priority:0
Work that we can't release without
User Story
A single user-facing feature. Can be grouped under an epic.
Milestone
As an Android/IOS application developer I want to build a configuration of my application using dotnet CLI that includes Diagnostics Classes/EventPipe/Diagnostic Server, so that I can use existing dotnet-* tooling and PerfView for on device debugging and profiling.
Description
To use diagnostic tooling, application needs to include custom implemented EventListeners, EventSources, managed diagnostic classes, native EventPipe library and native Diagnostic Server library. Since all that could make a significant impact on application size (very important for Android/IOS developers), we should exclude all those components in retail builds that will be pass for certification and published in app stores (at least the EventPipe/Diagnostic Server). Since a lot of the diagnostic tasks related to EventPipe handles performance, it still make sense to include all of the above in a configuration that will be as close to the retail build as possible, full optimization (full AOT build on platforms demanding it) and full IL linking. It also needs to be clear to developers that this configuration is not intended for certification, just for profiling and performance testing. Regular debug builds should also include all needed components to be able to run dotnet-* tooling against running application on device.
Tasks
The text was updated successfully, but these errors were encountered: