OwningComponentBase doesn't implement IAsyncDisposable

[SteveSandersonMS]

Reported at #25817

When we implemented IAsyncDisposable in components we should probably have also added support for this on OwningComponentBase.

I'm not 100% certain whether adding it would count as a breaking change. To follow existing patterns, we'd want to implement IAsyncDisposable.DisposeAsync explicitly and also add a protected virtual DisposeAsync(bool disposing), but that would likely clash with anybody's existing IAsyncDisposable implementation in existing subclasses. People would have to change their IAsyncDisposable implementations to override the new base-class DisposeAsync method. So I guess it's quite breaking.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[berhir]

What is the recommended way of using the OwningComponentBase with IAsyncDisposable?
I am facing two problems with it:

1. When my component implements IAsyncDisposable

In this case, the Dispose() method of the OwningComponentBase gets not called automatically and I must call it manually.
This is something that many developers will miss because it's not obvious (there is no warning or error).

public async ValueTask DisposeAsync()
{
    // ...
    
    // Call Dispose of the OwningComponentBase to dispose the scope
    (this as IDisposable).Dispose();
}

2. The injected service implements IAsyncDisposable

In this case, I get an exception:
System.InvalidOperationException: 'MyService' type only implements IAsyncDisposable. Use DisposeAsync to dispose the container.

The workaround is to implement IAsyncDisposable in my component and dispose the scope manually.

public async ValueTask DisposeAsync()
{
    await (this.ScopedServices as IAsyncDisposable).DisposeAsync();
}

_
Is this the only way to do it or do I miss something?
Both cases are very common and should be handled by the OwningComponentBase automatically.

[tma-lawo]

Very annoying issue. I'm surprised that so few are affected by this. I have a SignalR-based messaging service scoped to a single component (imagine a chatbox somewhere on a webpage), and I want to be able to call await DisposeAsync on the HubConnection, so my service is also IAsyncDisposable.