Open mccreah opened 2 years ago
The issue was that the WS service was not registered with DI as either Singleton or Scoped. Without that registration the service works when it only has the default constructor.
But if you add a new constructor with dependencies and register those dependencies with DI you also have to register the service itself with the DI. Somewhat counterintuitive and not the same as it is with MVC controllers. Especially since one registration already happens with the UseServiceModel call.
// register the custom utility service
builder.Services.AddSingleton<IUtilityService, UtilityService>();
// if Service1 depends on IUtilityService you also need this! register the `Service` class with Dependency Injection, based on it being a single instance
builder.Services.AddSingleton<Service1>();
Which sample is the bug for
DI logging in a template that was made without Minimal API use
Please see an example here https://github.com/mccreah/samples
Describe the bug
No matter what I do and how I register various business services I will always get the following exception on service calls:
Exception details only:
To Reproduce Steps to reproduce the behavior:
Expected behavior No exception, service constructor should be called. The way it works in the Minimal API example.
Repo environment (please complete the following information):
Additional context
If this issue should've been opened in the main CoreWCF repo, feel free to move it there.