The DNAA0001 analyzer was incorrectly triggering warnings for Application classes that use C# 12 primary constructors with the correct activation constructor signature. Additionally, the analyzer tests were not appearing in the Azure DevOps test results panel, making them difficult to discover and filter.

Consider this example:

[Application]
public class MainApplication(IntPtr handle, JniHandleOwnership ownership) : Application(handle, ownership)
{
    protected override MauiApp CreateMauiApp() => MauiProgram.CreateMauiApp();
}

This would incorrectly show: DNAA0001: Application class 'MainApplication' does not have an Activation Constructor 'MainApplication(IntPtr handle, JniHandleOwnership transfer)'

Root Cause

The analyzer only checked for traditional ConstructorDeclarationSyntax nodes in class members, but C# 12 primary constructors are declared at the class level using parameters on the class name itself. Additionally, the test pipeline wasn't publishing test results to Azure DevOps.

Solution

• Analyzer Fix: Refactored to use symbol-based analysis instead of syntax-based analysis
• Test Visibility: Enhanced CI pipeline to publish test results for better discoverability
• Use INamedTypeSymbol.Constructors to automatically handle all constructor types (primary, traditional, partial)
• Replaced manual string parsing with robust semantic type checking using IParameterSymbol.Type
• Added test result publishing support to run-dotnet-preview.yaml template
• Updated build pipeline to publish Microsoft.Android.Sdk.Analysis test results with proper title

The analyzer now correctly recognizes both traditional constructors and primary constructors with the required (IntPtr handle, JniHandleOwnership ownership) signature, and tests now appear in the Azure DevOps test results panel where they can be filtered by "DNAA0001".

Fixes #10425.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.