<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Csharp on Corey Leavitt</title>
    <link>https://blog.leavitt.dev/tags/csharp/</link>
    <description>Recent content in Csharp on Corey Leavitt</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 07 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.leavitt.dev/tags/csharp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Never re-initialize the camera in-process on Windows</title>
      <link>https://blog.leavitt.dev/posts/windows-frameserver-wedge/</link>
      <pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.leavitt.dev/posts/windows-frameserver-wedge/</guid>
      <description>Tearing down and re-creating a MediaCapture inside a running process can wedge the Windows Camera Frame Server for the whole machine, with a persistent E_HANDLE until the service is restarted. The only reliable recovery is a fresh process, and the fix that stuck was deleting the code that could do otherwise.</description>
    </item>
  </channel>
</rss>
