<?xml version="1.0" encoding="UTF-8" standalone="no"?><feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://docs.lextudio.com/blog/</id>
  <title>Lex Li's blog posts</title>
  <subtitle>All blog posts Lex Li (lextm) made.</subtitle>
  <updated>2026-05-25T19:06:07-04:00</updated>
  <author>
    <name>Lex Li</name>
    <uri>https://docs.lextudio.com/blog/</uri>
  </author>
  <link href="https://docs.lextudio.com/blog/feed.xml" rel="self" type="application/atom+xml"/>
  <link href="https://docs.lextudio.com/blog/" hreflang="en" rel="alternate" type="text/html"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 Lex Li </rights>
  <icon>/blog/assets/img/favicons/favicon.ico</icon>
  <logo>/blog/assets/img/favicons/favicon-96x96.png</logo>


  
  <xhtml:meta content="noindex" name="robots" xmlns:xhtml="http://www.w3.org/1999/xhtml"/><entry>
    <title>DevFlow for WPF: Modern tooling for .NET 8+ desktop apps</title>
    <link href="https://docs.lextudio.com/blog/devflow-for-wpf/" rel="alternate" title="DevFlow for WPF: Modern tooling for .NET 8+ desktop apps" type="text/html"/>
    <published>2026-05-22T00:00:00-04:00</published>
  
    <updated>2026-05-22T00:00:00-04:00</updated>
  
    <id>https://docs.lextudio.com/blog/devflow-for-wpf/</id>
    <content src="https://docs.lextudio.com/blog/devflow-for-wpf/" type="text/html"/>
    <author>
      <name>Lex Li</name>
    </author>

  
    
    <category term="Frameworks and Libraries"/>
    
  

  <summary>DevFlow is the modern developer loop Microsoft has been building around MAUI. This post explains how LeXtudio is bringing the same live, runtime-aware workflow to WPF on .NET 8+.</summary>

  </entry>

  
  <entry>
    <title>My Emails to AvaloniaUI</title>
    <link href="https://docs.lextudio.com/blog/avalonia-emails-published/" rel="alternate" title="My Emails to AvaloniaUI" type="text/html"/>
    <published>2026-04-16T00:00:00-04:00</published>
  
    <updated>2026-04-16T00:00:00-04:00</updated>
  
    <id>https://docs.lextudio.com/blog/avalonia-emails-published/</id>
    <content src="https://docs.lextudio.com/blog/avalonia-emails-published/" type="text/html"/>
    <author>
      <name>Lex Li</name>
    </author>

  
    
    <category term="Tools and Platforms"/>
    
  

  <summary>Several emails I sent to the AvaloniaUI team, covering business inquiries and proposed collaboration details. The purpose of sharing these emails is to promote transparency and provide reference to avoid misunderstandings in the community.</summary>

  </entry>

  
  <entry>
    <title>WPF in VS Code: From Fragmented Tooling to Integrated Experience</title>
    <link href="https://docs.lextudio.com/blog/wpf-in-vscode-from-fragmented-tooling-to-integrated-experience/" rel="alternate" title="WPF in VS Code: From Fragmented Tooling to Integrated Experience" type="text/html"/>
    <published>2026-04-01T20:00:00-04:00</published>
  
    <updated>2026-04-01T20:00:00-04:00</updated>
  
    <id>https://docs.lextudio.com/blog/wpf-in-vscode-from-fragmented-tooling-to-integrated-experience/</id>
    <content src="https://docs.lextudio.com/blog/wpf-in-vscode-from-fragmented-tooling-to-integrated-experience/" type="text/html"/>
    <author>
      <name>Lex Li</name>
    </author>

  
    
    <category term=".NET"/>
    
    <category term="WPF"/>
    
    <category term="Tooling"/>
    
    <category term="VS Code"/>
    
  

  <summary>How fragmented C# and XAML tooling left WPF developers in VS Code without a complete solution—and how integrating community-built components creates the modern experience that was missing.</summary>

  </entry>

  
  <entry>
    <title>A Brief History of .NET Documentation Tools, and Why I Built dotnet-sphinx</title>
    <link href="https://docs.lextudio.com/blog/a-brief-history-of-dotnet-documentation-tools-and-the-new-dotnet-sphinx/" rel="alternate" title="A Brief History of .NET Documentation Tools, and Why I Built dotnet-sphinx" type="text/html"/>
    <published>2026-03-16T00:00:00-04:00</published>
  
    <updated>2026-03-16T00:00:00-04:00</updated>
  
    <id>https://docs.lextudio.com/blog/a-brief-history-of-dotnet-documentation-tools-and-the-new-dotnet-sphinx/</id>
    <content src="https://docs.lextudio.com/blog/a-brief-history-of-dotnet-documentation-tools-and-the-new-dotnet-sphinx/" type="text/html"/>
    <author>
      <name>Lex Li</name>
    </author>

  
    
    <category term="Tools and Platforms"/>
    
  

  <summary>A journey through .NET documentation tooling history—from NDoc to Sandcastle to modern gaps, and how Lunet and dotnet-sphinx bridge the ecosystem for open source projects.</summary>

  </entry>

  
  <entry>
    <title>Alternative Avalon Universe: Open Alternatives to Closed-Source Tooling</title>
    <link href="https://docs.lextudio.com/blog/alternative-avalon-universe-open-alternatives-to-closed-source-tooling/" rel="alternate" title="Alternative Avalon Universe: Open Alternatives to Closed-Source Tooling" type="text/html"/>
    <published>2026-03-02T00:00:00-05:00</published>
  
    <updated>2026-03-02T00:00:00-05:00</updated>
  
    <id>https://docs.lextudio.com/blog/alternative-avalon-universe-open-alternatives-to-closed-source-tooling/</id>
    <content src="https://docs.lextudio.com/blog/alternative-avalon-universe-open-alternatives-to-closed-source-tooling/" type="text/html"/>
    <author>
      <name>Lex Li</name>
    </author>

  
    
    <category term="Tools and Platforms"/>
    
  

  <summary>A practical guide to community-built open alternatives for Avalonia development. Covers VS Code and Visual Studio extensions, DataGrid solutions, and emerging frameworks that offer clear licensing and governance.</summary>

  </entry>

</feed>