Generated ClientSettings Don't Compile if BindCore is Customized

[jorgerangel-msft]

If the protected override void BindCore(IConfigurationSection section) of the generated ClientSettings type is moved to custom code, we still generate a partial implementation but the generated xml docs reference a type with a missing import statement:

using System.ClientModel.Primitives;
using System.Diagnostics.CodeAnalysis;

namespace Azure.Storage.Queues
{
    /// <summary> Represents the settings used to configure a <see cref="QueueClient"/> that can be loaded from an <see cref="IConfigurationSection"/>. </summary>
    [Experimental("SCME0002")]
    public partial class QueueClientSettings : ClientSettings
    {
        /// <summary> Gets or sets the Options. </summary>
        public QueueClientOptions Options { get; set; }
    }
}

The using Microsoft.Extensions.Configuration; is not being added despite us referencing IConfigurationSection in the generated xml doc

[github-actions]

🎯 Issue Triage

When BindCore is moved to custom code, the generated partial ClientSettings class still references IConfigurationSection in its XML doc comment (<see cref="IConfigurationSection"/>), but the C# emitter fails to emit the required using Microsoft.Extensions.Configuration; directive, causing a compilation error.

Category: Bug
Area: emitter:client:csharp

⚠️ No reproduction provided. A minimal repro would help diagnose this issue.

🔍 Analysis

• The C# emitter tracks using directives for types used directly in code, but appears to miss types that are only referenced via XML doc <see cref="..."/> tags.
• The issue is conditional: it surfaces only when BindCore is customized (moved out of generated code). In the default (non-customized) path, BindCore itself imports IConfigurationSection directly as a parameter type, so the using is added. When it moves to custom code, the generated partial class loses the method but retains the XML doc reference — without the associated using.
• Affected component: ClientSettings code generation in @typespec/http-client-csharp, specifically the logic that determines required using directives when partial customization removes certain members.

📝 Suggested next steps

• Identify where using directives are collected for the ClientSettings partial class generation.
• Ensure that types referenced in XML doc <see cref="..."/> strings also trigger the appropriate using directive, or that the IConfigurationSection reference is conditionally included regardless of BindCore presence.
• Add a test covering the customized-BindCore scenario to verify the generated file compiles.

Generated by Agentic Triage