No Scope available on non-versioned controllers

[twenzel]

Given:
ASP.NET Core 5 API App using Windsor

When using Microsoft API versioning (Startup.cs line 29) the controller is only working when the request is using the versioned url "/api/v1/weatherforecast". When using the non-versioned url "/weatherforecast" services resolved inplace creates a InvalidOperationException "No Scope available"

This was working with ASP.NET Core 2.2.

AspCoreVersionedApis.zip

[ltines]

HI @twenzel
preferred way to resolve components in web code is to use IServiceProvider not container directly. Especially with scoped services. ASP.NET runtime contols the lifetime of the scope.

For your code:

public WeatherForecastController(ILogger<WeatherForecastController> logger, IUserService userService, IServiceProvider serviceProvider)
{
	_logger = logger;
	_userService = userService ?? throw new ArgumentNullException(nameof(userService));
	_serviceProvider = serviceProvider;
}

[HttpGet]
public IEnumerable<WeatherForecast> Get()
{
	var service = _serviceProvider.GetRequiredService<IScopedService>();
	var service1 = _serviceProvider.GetRequiredService<ITransientService>();

	var rng = new Random();
	return Enumerable.Range(1, 5).Select(index => new WeatherForecast
	{
		Date = DateTime.Now.AddDays(index),
		TemperatureC = rng.Next(-20, 55),
		Summary = Summaries[rng.Next(Summaries.Length)]
	})
	.ToArray();
}

[StefanoVuerich]

Hi Guys,

@ltines

I'm experiencing the same issue as @twenzel . I have a POST request, then my code calls Container.BeginScope().
The scope seems to be ok, as I don't receive any exception.
When I try to resolve a scoped service I get error: System.InvalidOperationException: 'No scope available'.

If, in the non api versioned controller, I wrap my code in using(var scope = HttpContext.RequestServices.CreateScope()), then everything works fine.
But I want the scope to be created automatically for each non api versioned controller.

Do you have any suggestion?

Best regards

[ltines]

@StefanoVuerich ,

i am wondering why do you need to manually call Container.BeginScope()? The pipeline should start scope via CreateScope automatically

[StefanoVuerich]

@ltines ,

our old implementation was calling Container.Beginscope() to be able to resolve scoped services.

What is the piece of the pipeline you are referring when you say 'The pipeline should start scope via CreateScope automatically' ?