ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #csharp
When an ASP.NET Core application hosted on Kestrel receives a sudden burst of concurrent requests, the .NET ThreadPool's hill-climbing algorithm may not inject worker threads quickly enough, causing requests to queue and latency to spike. The core uncertainty is where the boundary lies between a transient burst that the pool should absorb and sustained starv
Synchronization Context Capture \n In C# asynchronous programming, the await operator captures the current SynchronizationContext by default to ensure the continuation runs on the original thread. This is essential for updating UI elements in frameworks like WPF or WinForms. \n To optimize performance and avoid potential deadlocks in library code, ConfigureA
Goal: Confirm whether returning true from HttpClientHandler.ServerCertificateCustomValidationCallback reliably suppresses platform certificate chain building and revocation checking in .NET 6 through .NET 9. Uncertainty: Windows (Schannel), Linux (OpenSSL), and macOS (SecureTransport) invoke the callback at different points in validation. CheckCertificateRev
Goal Ensure that all parts of a partial class share the same accessibility modifier so that an unintentional public exposure does not occur. Constraints The current C# compiler (Roslyn) silently merges partial class parts, taking the most permissive modifier without any warning or error. This behavior can cause a type intended to be internal to become public
In .NET 6, developers often use ILogger.BeginScope to set a minimum log level for a block of code, hoping to suppress noisy alerts. However, some logging providers do not honor these scoped levels automatically, leading to inconsistent noise suppression across the application. The goal is to reduce notification noise by applying scoped log levels uniformly,
Rollback behavior limits ClickOnce provides an automatic rollback mechanism that restores the previous version when an update deployment fails before the new version is marked active. This behavior depends on the presence of an <update> element with an expiration attribute in the deployment manifest. However, the mechanism is not guaranteed in all fail
The `using` statement is compiled into a `try { … } finally { obj.Dispose(); }` construct, guaranteeing disposal when the block exits. In an async method, the `await` keyword can suspend execution at any intermediate point, but the exact moment `Dispose` runs relative to that suspension remains unspecified for pre‑C# 8 code. This uncertainty impacts determin
The objective is to define a reliable verification workflow for System.IO.File.Replace when a backup is used to restore a file, ensuring byte‑level integrity and preserving metadata across supported .NET versions and file systems. Key constraints include the fact that File.Replace does not provide a built-in hash, creates a backup copy of the destination, an
When deploying a C# application as a self‑contained package, I need to ensure the correct .NET runtime is bundled while also controlling which SDK version is used for building and publishing across different operating systems. The CLI chooses the latest SDK unless a global.json overrides it, and runtime roll‑forward can affect which version runs on target ma