CoreWCF / CoreWCF/samples

Logging DI sample does not work in a template without Minimal APIs

Open
#18 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
50
Forks
22
PR merge metrics
No merged PRs in 30d

Description

**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:

```



a:InternalServiceFault
The service implementation object was not initialized or is not available.




The service implementation object was not initialized or is not available.
at CoreWCF.Dispatcher.SyncMethodInvoker.InvokeAsync(Object instance, Object[] inputs)
at CoreWCF.Dispatcher.DispatchOperationRuntime.<>c__DisplayClass68_0.<<InvokeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at CoreWCF.Dispatcher.DispatchOperationRuntime.InvokeAsync(MessageRpc rpc)
at CoreWCF.Dispatcher.DispatchOperationRuntime.InvokeAsync(MessageRpc rpc)
at CoreWCF.Dispatcher.ImmutableDispatchRuntime.ProcessMessageAsync(MessageRpc rpc)
at CoreWCF.Dispatcher.MessageRpc.ProcessAsync(Boolean isOperationContextSet)
System.InvalidOperationException



```

Exception details only:

```



The service implementation object was not initialized or is not available.
at CoreWCF.Dispatcher.SyncMethodInvoker.InvokeAsync(Object instance, Object[] inputs)
at CoreWCF.Dispatcher.DispatchOperationRuntime.<>c__DisplayClass68_0.<<InvokeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at CoreWCF.Dispatcher.DispatchOperationRuntime.InvokeAsync(MessageRpc rpc)
at CoreWCF.Dispatcher.DispatchOperationRuntime.InvokeAsync(MessageRpc rpc)
at CoreWCF.Dispatcher.ImmutableDispatchRuntime.ProcessMessageAsync(MessageRpc rpc)
at CoreWCF.Dispatcher.MessageRpc.ProcessAsync(Boolean isOperationContextSet)
System.InvalidOperationException

```

**To Reproduce**
Steps to reproduce the behavior:

1. Clone my samples repo and run the other app LoggingSampleNoMinimalApis.
2. Make a SOAP request to the service.
3. Exception always occurs, service contructor is never hit when debugging.

**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):**
- Windows 10
- x64
- .NET 6
- VS 2022

**Additional context**

If this issue should've been opened in the main CoreWCF repo, feel free to move it there.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.