Using both `Microsoft.AspNetCore.Components.WebView.Wpf` and `Microsoft.Extensions.Options.ConfigurationExtensions` cause SelfContained publish failed in VS

[tp1415926535]

Description

If install the Microsoft.AspNetCore.Components.WebView.Wpf NuGet package and use functions from Microsoft.Extensions.Options.ConfigurationExtensions, SelfContained publish in Visual Studio publish page will fail, but it works fine when using the command line dotnet publish -c Release -r win-x64 --self-contained true. If the “obj” folder is not deleted after running the command, the page will also publish successfully.

Reproduction Steps

1. Create a WPF application ( .net9 or 10 ) , install the Microsoft.AspNetCore.Components.WebView.Wpf NuGet package, and change the SDK to “Microsoft.NET.Sdk.Razor” to ensure successful compilation.
2. If the webView nuget package just installed is version earlier than 10.0, install Microsoft.Extensions.Options.ConfigurationExtensions as well; otherwise, the package already includes this.
3. Call the function public static IServiceCollection Configure<TOptions>(this IServiceCollection services, IConfiguration config), for example:

    var serviceCollection = new ServiceCollection();
    var configuration = new ConfigurationBuilder()
        .AddJsonFile("appsettings.json", optional: true).Build();
    serviceCollection.Configure<TestOption>(configuration);

public class TestOption { }

4. Right-click the project, select publish, choose folder and SelfContained release x64 , click “Publish,” and an error occurs.

Expected behavior

The button on the publish page should function normally, just like the output of a command-line execution.

Actual behavior

A window pops up indicating a publishing error, but no specific reason is shown.

Regression?

No response

Known Workarounds

Add the following property to PropertyGroup like:

<PropertyGroup>
    <InterceptorsNamespaces>$(InterceptorsNamespaces);Microsoft.Extensions.Configuration.Binder.SourceGeneration</InterceptorsNamespaces>
</PropertyGroup>

Or using the command line.

Impact

All packages that directly or indirectly reference Microsoft.Extensions.Options.ConfigurationExtensions, such as Microsoft.Extensions.Hosting

Configuration

No response

Other information

No response

[amarinov-msft]

Hello @tp1415926535
I tried to reproduce your scenario, following the provided steps, but the project seems to be publishing fine. I tested in .NET 9 - SelfContained release x64.
Can you please share a minimal repro that demonstrates this issue?
Any additional information about the environment you are using may also be of help.

[tp1415926535]

Hello @tp1415926535 I tried to reproduce your scenario, following the provided steps, but the project seems to be publishing fine. I tested in .NET 9 - SelfContained release x64. Can you please share a minimal repro that demonstrates this issue? Any additional information about the environment you are using may also be of help.

WpfBlazorTest.zip

[tp1415926535]

Hello @tp1415926535 I tried to reproduce your scenario, following the provided steps, but the project seems to be publishing fine. I tested in .NET 9 - SelfContained release x64. Can you please share a minimal repro that demonstrates this issue? Any additional information about the environment you are using may also be of help.

I previously posted a .NET 10 example. If you don't have VS 2026, here is the same example for .NET 9.

WpfBlazorTest.NET9.zip

[amarinov-msft]

Thank you for providing the repros. I was able to reproduce the issue with your .NET 10 example. We will investigate this and will keep you updated.

[amarinov-msft]

I confirmed that this is an issue in the WPF SDK and needs to be investigated further. The actual error the VS Publish dialog hides is:

  BindingExtensions.g.cs(40,10): error CS9137: The 'interceptors' feature is not enabled in this namespace.
  Add '<InterceptorsNamespaces>$(InterceptorsNamespaces);Microsoft.Extensions.Configuration.Binder.SourceGeneration</InterceptorsNamespaces>' to your project.
  […\<project>_<hash>_wpftmp.csproj]

The failure happens inside the temporary *_wpftmp.csproj that the WPF SDK's two-pass markup compile (GenerateTemporaryTargetAssembly) builds. That temp project ends up with the Microsoft.Extensions.Configuration.Binder source generator active but without the matching InterceptorsPreviewNamespaces allow-list that the binder package normally pairs with it - so csc rejects the generated interceptor and the publish aborts before the main project is even compiled. Your <InterceptorsNamespaces> workaround fixes it because that property does propagate into the temp project.

[tp1415926535]

The actual error the VS Publish dialog hides is

In fact, I’ve encountered a lot of publish errors before, but the console output has never been helpful, and the error pop-ups just point to meaningless logs on the C drive. So if possible, I hope that the actual errors can be displayed, rather than having to guess, experiment, and troubleshoot every time.