You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merely using the 5.0 code in an app generated from the 6.0 project template doesn't seem to even register the service in the first place (i.e., builder.Services.AddTransient<TransientDisposable>();); therefore, there's no service to inject into the component.
If that's an OOB behavior now, then the Detect transient disposables section should be removed and the NOTE in the Utility base component classes to manage a DI scope section can be replaced with a sentence or two about how transients aren't registered by default when dev code attempts to do so.
If it isn't an OOB feature now and something else is going on, I'll need more info and a revised DetectIncorrectUsagesOfTransientDisposables.cs (preferbly with the NRT updates for 6.0) along with any updates to Program.cs for WASM/Server scenarios.
I'll mark this for work post 6.0 RC2 release. In the meantime, I'll remove the section from the 6.0 preview doc so as not to confuse any readers at this time.
The
Startup
πProgram
changes this morning (10/7) will break the 6.0 preview doc for the transient dep example.Document Details
β Do not edit this section. It is required for docs.microsoft.com β GitHub issue linking.
The text was updated successfully, but these errors were encountered: