System.InvalidOperationException for XmlCommentsParameterFilter

[sgoldberg16]

I am having the following exception throw after upgrading to .Net8:
System.InvalidOperationException: A suitable constructor for type 'Swashbuckle.AspNetCore.SwaggerGen.XmlCommentsParameterFilter' could not be located. Ensure the type is concrete and all parameters of a public constructor are either registered as services or passed as arguments. Also ensure no extraneous arguments are provided.

Any initial thoughts or suggested fixes would be appreciated!
Using Swashbuckle.AspNetCore 6.5.0
Using Swashbuckle.AspNetCore.SwaggerUI 6.5.0
Using Swashbuckle.AspNetCore.SwaggerGen 6.5.0
Using Swashbuckle.AspNetCore.Swagger 6.5.0

[KothariDhrumil]

I am also facing the same when I am publishing this on IIS. in local its working fine.

[KothariDhrumil]

[Havunen]

Have you tested with https://github.com/Havunen/DotSwashbuckle https://www.nuget.org/packages/DotSwashbuckle.AspNetCore

[martincostello]

It's not obvious to me at first glance why this wouldn't be working.

The activation call comes from here:

Swashbuckle.AspNetCore/src/Swashbuckle.AspNetCore.SwaggerGen/DependencyInjection/ConfigureSwaggerGeneratorOptions.cs

Lines 76 to 77 in 830c5a6

	return (TFilter)ActivatorUtilities
	.CreateInstance(_serviceProvider, filterDescriptor.Type, filterDescriptor.Arguments);

The constructor receives a single XPathDocument:

Swashbuckle.AspNetCore/src/Swashbuckle.AspNetCore.SwaggerGen/XmlComments/XmlCommentsParameterFilter.cs

Line 11 in 830c5a6

public XmlCommentsParameterFilter(XPathDocument xmlDoc)

Which is provided as the argument here:

Swashbuckle.AspNetCore/src/Swashbuckle.AspNetCore.SwaggerGen/DependencyInjection/SwaggerGenOptionsExtensions.cs

Line 433 in 830c5a6

swaggerGenOptions.ParameterFilter<XmlCommentsParameterFilter>(xmlDoc);

It might be related to this breaking change in .NET 8.

[martincostello]

Having updated Swashbuckle to target net8.0, I can't replicate this with our test suite.

Please provide a minimal reproducible example as a GitHub repository that demonstrates the issue you're experiencing so we can look into this further.