ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #dotnetcore
Learn how to choose between Transient, Scoped, and Singleton lifetimes in .NET Core to avoid memory leaks and captive dependency errors.
Learn how to avoid Captive Dependencies in .NET Core by properly managing Scoped lifetimes, especially when integrating database contexts into background services.
Decide between MVC and Razor Pages for a new ASP.NET Core web app by weighing routing, boilerplate, and testability. Includes a side‑by‑side CRUD example and verification steps.
Singleton, Scoped, or Transient? A concrete, runnable example shows how ASP.NET Core service lifetimes behave, how scoped-from-singleton captures cause cross-request bugs, and how to catch them at startup.
Map each ASP.NET Core DI failure — missing registrations, scoped-from-singleton captures, circular dependencies, empty IEnumerable injections — to the check that confirms it and the fix that actually matches.
I have a .NET Core web application that streams telemetry to an Application Insights resource. Smart detection is enabled by default and sends email notifications for each detected anomaly, which results in a high volume of messages that include low‑severity performance degradations and occasional false positives. I would like to keep the automatic analysis
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?