.NET Packages

Use Ansight.Maui for a .NET MAUI app and Ansight for a native .NET Android, iOS, or Mac Catalyst app. These all-in-one packages are the shortest path through the .NET quickstart.

Choose Ansight.Core only when the app needs manual runtime and tool registration.

Supported Targets

The core package targets:

• net9.0
• net9.0-android
• net9.0-ios
• net9.0-maccatalyst

Runtime and Workflow Packages

The NuGet badges link to each package and show its current release version.

Package	NuGet	Use when	Includes
Ansight		You want the standard non-MAUI app setup.	Ansight.Core, native pairing where supported, all non-MAUI remote tool packages including Clipboard, opt-in connectivity and motion capture, annotated feedback, offline capture, and the WithAnsightSdk(...) setup API.
Ansight.Maui		You are integrating a .NET MAUI app.	Ansight, Ansight.Tools.Maui, annotated feedback, offline capture, and MauiAppBuilder setup helpers.
Ansight.Core		You want direct control over runtime and tool registration.	Core runtime, telemetry, network capture, pairing protocol, purchase diagnostics, tool abstractions, host connection, JPEG capture, and build-time safety targets.
Ansight.Pairing		A core-only mobile app should own native QR acquisition.	Native iOS and Android pairing acquisition.
Ansight.Motion		You want app-fed motion evidence with a core-only integration.	Opt-in shake and accelerometer forwarding.
Ansight.Connectivity		You want passive connection state and quality evidence.	Opt-in native mobile observations and portable desktop availability; included by Ansight.
Ansight.Annotations		You want Debug-only annotated in-app feedback without an all-in-one package.	Native editor, screenshot and visual-tree evidence, hooks, artifacts, outbox, and live/offline delivery.
Ansight.OfflineCapture		You want evidence capture without a live host connection.	Local storage, retention, runtime mutation, network and connectivity evidence, screenshots, annotation bundles, and ZIP/AES export. Team upload requires the separate Ansight.Cloud.OfflineCapture integration.
Ansight.Profiling.DotNet (Beta)		You want the beta CLI workflow to profile a prepared .NET Android or iOS artifact.	Diagnostic endpoint configuration, target manifest, and an exact application-ready marker. See Startup Profiling.

The runtime namespace remains Ansight even when the NuGet package id is Ansight.Core. The all-in-one packages register annotated feedback by default in Debug application builds. Offline capture starts only when configured and initialized by the app; motion capture requires WithMotionCapture() and connectivity requires WithConnectivityCapture().

What Ansight.Core Includes

• sampling and retention configuration
• built-in memory and FPS metrics
• opt-in battery, open-file-handle, and Android JNI-reference-count metrics
• screen-view, lifecycle, log, custom channel, screenshot, and touch capture
• durable native crash capture and next-launch delivery
• process-wide and explicit HTTP request/response capture with app-side sanitization
• simulator/emulator-only purchase observations and validation
• app artifact providers and streamed artifact requests
• package-owned runtime extensions through IRuntimeFeature
• runtime-owned host connection and reconnection
• opt-in cellular connection policy and native unattended test provisioning
• tool abstractions, custom tools, tool guard policy, and build-time enforcement

Tool Packages

Install tool packages separately only when using Ansight.Core. The all-in-one packages already include their respective tool sets.

Tool	Package	NuGet
VisualTree	Ansight.Tools.VisualTree
MAUI	Ansight.Tools.Maui
Reflection	Ansight.Tools.Reflection
Database	Ansight.Tools.Database
FileSystem	Ansight.Tools.FileSystem
Preferences	Ansight.Tools.Preferences
SecureStorage	Ansight.Tools.SecureStorage
Clipboard	Ansight.Tools.Clipboard

See the complete remote tools guide for registration APIs, capabilities, and guard policy.

Core-Only Installation

dotnet add package Ansight.Core

Add Ansight.Pairing separately when a core-only app should own native QR acquisition. Add individual Ansight.Tools.* packages only for the tool suites the workflow needs.

Follow .NET Setup for the recommended all-in-one installation and startup flow. Review .NET Security before choosing the package layout for distributable builds.