Peter Morris
Peter Morris
@SteveSandersonMS To be clear, my suggestion isn't to have a new scope for every component, it was to allow the developer to specify their component should have a new scope...
> With transient, you always get a new instance each time you ask for one. https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-6.0 Oooh, thanks for setting me straight on my misunderstanding! I always thought it was...
> * when the time comes to dispose, check the weak pointer to see if it is still alive and dispose accordingly The question in this issue though is, when...
I've implemented this in v6 by dropping IDisposable in the Blazor libraries and going only with IAsyncDisposable, as I know for certain this will be called. Thank you!
I have it ready, but I am still unsure about it. Anyone who needs it could implement it themselves, and then call Dispose.
If you wanted to async dispose something in your code and had to implement IAsyncDisposable, what would the code look like?
Fixed in 6.0
I'm going through the motions now. Checking github issues to see what I should include.
I really needed this today, for my C# language templating plugin.
I'm sorry, I don't know the answer to this question. Have you asked in Moq?