{
  "id": 3374967,
  "title": ".NET 10 BufferedStream WriteByte: Flush Full Buffers Explicitly",
  "url": "https://urgent.news/2026/08/25/net-10-bufferedstream-writebyte-flush-full-buffers-explicitly",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-25T23:26:11.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ssukhpinder/net-10-bufferedstream-writebyte-flush-full-buffers-explicitly-45a2"
  },
  "original_language": "en",
  "account": null,
  "summary": "In .NET 10, the behavior of BufferedStream.WriteByte has changed, removing the implicit flush that occurred at the internal capacity boundary. This change was introduced in .NET 10 LTS, not as a preview feature, and is stable behavior. The modification affects applications that rely on the previous behavior of Flush() being called at the capacity boundary, particularly when using custom streams, protocol adapters, compressors, or test doubles where Flush() has additional meaning. The change ensures that bytes can still be moved to the underlying stream when the buffer needs more space, but the capacity boundary no longer results in an accidental flush. Microsoft documents this behavior change for .NET 10, emphasizing that WriteByte now differs from other BufferedStream.Write methods in its behavior.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}