Triage notes on Microsoft.Extensions areas

triage.md

Issues to consider for 6.0 on Extensions:

Presentation DI+HttpClientFactory

• https://andrewlock.net/exporing-the-code-behind-ihttpclientfactory/

Meta:

• Nullable annotations: #43605
• API documentation debt on each of the areas: e.g #43871 and about 10 more similar.
• General documentation regarding extensions: Currently docs are spread between both dotnet/docs and dotnet/AspNetCore.Docs. Would be good to drive an effort to ensure the ASP.NET Core docs have been sufficiently refactored to focus on web-specific examples and reduce duplication with docs in dotnet/docs (representing the basis for all .NET workloads, not just web), while ensuring the ASP.NET Core docs also maintain their own set of web focused content for Extensions.

Triage: Configuration

• https://github.com/microsoft/reverse-proxy/blob/master/src/ReverseProxy/Utilities/ConfigurationReadingExtensions.cs bind... todo doc page

• To be treated as maintainence mode. Features were complete for aspnet team. Unless we find improvements to make to support WPF/WinForms/Xamarin scenarios

• Plan is to push back on new feature requests unless the can be opt-in behaviors. Generally it's pretty easy to implement your own configuration provider, so they always have a workaround with most open issues.

• Found some issues dealing with the way we do key handling in configuration: (two escaping issues: #42643, #35989) and #40911

• Investments that would make configuration better/faster/smarter add huge value here. (e.g. #43930, 36130, or perhaps #36010)

Triage Options:

• High votes: Options Validation #36391
• #43662
• #43359

Triage: DependencyInjection

• Deadlock improvements, involves code refactoring
• DI validation
• DI diagnostics

Triage Hosting:

Trendy issues:

• Xamarin issue #35993

• WinForms #35998

• WPF #36085

• Making Startup methods async, related issues: #36124, #1171

• UseStartup from IWebHostBuilder #42364

• #36017 related to #35991 BackgroundService TaskStatus

Triage: Logging

• https://github.com/geeknoid/LoggingGenerator

• Structured Logging has high votes (#35995). Needs meeting with partners to discuss (Noah, Riley, Sourabh)

• Sensitive data (#36006) (discuss with Sourabh)

• Logging Analyzers (e.g. #36020 and #36064) or to explore more scenarios which may have high value.

• EventSourceLogger improvements (33486 and 34739 and #36515)

Driving work for VT100 API addition into System.Console:

• Set foreground/background (TODO: create issue and add API proposal)

Driving work in System.Text.Json:

• For making PooledByteBufferWriter public #33598

Triage FileSystem:

• One perf issue from Ryan dotnet/runtime/issues/42036
• One PR currently in review to use Polling for PhysicalFileWatcher dotnet/runtime/issues/37664

Driving work in area-System.IO:

• new API request on System.IO for case sensitivity: dotnet/runtime/issues/35128
• FileSystemWatcher related #36091

Triage: Caching

We don't want to allow enumerating on keys while elemeents may get removed within another thread, (keeping as atomic operation). In order to allow for some of the feature requests in caching, (e.g. bulk remove) we can offer returning a snapshot (say array of elements. In this use case like wanting to remove with certain prefix "ZZZ", given the snapshot, will use TryGetValue and if already gone it would not throw. Below are the three related issues to consider:

• How to flush all cache #36547
• Bulk remove on IDistributedCache #36568 And also related to consider:
• Enumerating keys using IDistributedCache #36402

Perf issue: (Future) dotnet/runtime#36499

Triage Primitives:

• #36617 check proposed API that needs work