'interceptors' compiler error when trying to use request middleware? (and analyzer errors when added)

[bobby-driggs]

I am using the latest 15.1.11 HotChocolate packages (& .NET 9 SDK)

In fact - i was able to reproduce this error using the base hotchocolate graphql server template in setup.

If you try to utilize:

builder.AddGraphQL()
    .AddTypes()
    .UseRequest<SomeMiddleware>();

Where SomeMiddleware could be anything basic like:

internal class SomeMiddleware
{
    private readonly HotChocolate.Execution.RequestDelegate _next;
    
    public SomeMiddleware(
        HotChocolate.Execution.RequestDelegate next,
        IRequestExecutorOptionsAccessor options)
        {
            _next = next;
        }

    public async ValueTask InvokeAsync(IRequestContext context)
    {
        await _next(context);
    }
}

I get the following compiler error:

The interceptors feature is not enabled in this namespace. Add <InterceptorsNamespaces>$(InterceptorsNamespaces);HotChocolate.Execution.Generated</InterceptorsNamespaces> to your project.

So originally i do that, but after doing so, I started getting intermittent build errors related to analyzer files being broken, and the last straw i had, was when trying to generate an EF Core bundle (via cli), it complaining with the following error:

CS2001: ...HotChocolate.Execution.Generated could not be found and a secondary error with a leading ; In addition a bunch of analyzer errors like:

CS1504: "... Files\dotnet\sdk\... /analyzer:C:\Program" could not be opened

All of these extra problems go away if I dont use UseRequest and I remove the Interceptor namespace.

Ive noticed most of the examples are based on .NET 6 -> 8, and none seem to have this magical line about interceptors. even the ones that are using UseRequest. So either something is borked internally, or my machine is somehow non-standard?

Has anyone seen this? Its extremely frustrating, and hitting the build issue with EF Core is a bit of a last straw...