Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Add a note on Native AOT diagnostics support on iOS-like platforms #43399

Merged
merged 6 commits into from
Nov 15, 2024
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/core/deploying/native-aot/diagnostics.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,10 @@ ms.date: 08/07/2023

Native AOT shares some, but not all, diagnostics and instrumentation capabilities with CoreCLR. Because of CoreCLR's rich selection of diagnostic utilities, it's sometimes appropriate to diagnose and debug problems in CoreCLR. Apps that are [trim-compatible](../trimming/prepare-libraries-for-trimming.md) shouldn't have behavioral differences, so investigations often apply to both runtimes. Nonetheless, some information can only be gathered after publishing, so Native AOT also provides post-publish diagnostic tooling.

## .NET 8 Native AOT diagnostic support
## Native AOT diagnostic support

> [!NOTE]
> Starting from .NET 9, Native AOT supports targeting iOS-like platforms with .NET MAUI for which diagnostics support is described in the following [document](https://learn.microsoft.com/dotnet/maui/deployment/nativeaot?view=net-maui-9.0&preserve-view=true#native-aot-diagnostic-support-on-ios-and-mac-catalyst).
ivanpovazan marked this conversation as resolved.
Show resolved Hide resolved

The following table summarizes diagnostic features supported for Native AOT deployments:

Expand Down
Loading