<?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>Visual Studio Code | The .NET Blog</title><link>https://thedotnetblog.com/tags/visual-studio-code/</link><description>Articles, tutorials and insights from the .NET community.</description><generator>Hugo</generator><language>en</language><managingEditor>@thedotnetblog (The .NET Blog)</managingEditor><webMaster>@thedotnetblog</webMaster><lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thedotnetblog.com/tags/visual-studio-code/index.xml" rel="self" type="application/rss+xml"/><item><title>dotnet new WinUI: Create Windows Apps Without Touching Visual Studio</title><link>https://thedotnetblog.com/news/emiliano-montesdeoca/dotnet-new-winui-templates-cli-vscode/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><author>Emiliano Montesdeoca</author><guid>https://thedotnetblog.com/news/emiliano-montesdeoca/dotnet-new-winui-templates-cli-vscode/</guid><description>WinUI project templates now work from dotnet new — blank apps, NavigationView patterns, and more. VS Code support, no Visual Studio required, with Fluent Design defaults baked in.</description><content:encoded>&lt;p&gt;WinUI development used to require Visual Studio. That&amp;rsquo;s changing: Microsoft has published open-source project and item templates for WinUI that work with &lt;code&gt;dotnet new&lt;/code&gt;, bringing Windows app development into the standard CLI workflow.&lt;/p&gt;
&lt;h2 id="getting-started-in-three-commands"&gt;Getting Started in Three Commands&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-shell" data-lang="shell"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Install the templates&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;dotnet new install Microsoft.WindowsAppSDK.WinUI.CSharp.Templates
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Create a NavigationView app&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;dotnet new winui-navview -n MyApp
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Run it&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nb"&gt;cd&lt;/span&gt; MyApp
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;dotnet run
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;No Visual Studio, no manual project setup. The app runs from &lt;code&gt;dotnet run&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="whats-included"&gt;What&amp;rsquo;s Included&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Blank template&lt;/strong&gt; (&lt;code&gt;dotnet new winui&lt;/code&gt;) — a modern starting point with a Fluent title bar already wired up, updated default app icon with &lt;code&gt;.ico&lt;/code&gt; asset, proper light/dark mode defaults. Better than the old blank template that left you configuring the basics yourself.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;NavigationView template&lt;/strong&gt; (&lt;code&gt;dotnet new winui-navview&lt;/code&gt;) — the master-detail navigation pattern, fully wired up with a NavigationView, modern title bar, and multi-page navigation structure. Follows the standard Windows app silhouette for navigation-based apps. If you&amp;rsquo;re building anything with side navigation, start here.&lt;/p&gt;
&lt;p&gt;Both templates follow the &lt;a href="https://learn.microsoft.com/windows/apps/design/basics/app-silhouette"&gt;Windows app silhouettes&lt;/a&gt; — modern Fluent Design patterns for layout, navigation, and visual structure — out of the box.&lt;/p&gt;
&lt;h2 id="why-this-matters-for-non-visual-studio-developers"&gt;Why This Matters for Non-Visual-Studio Developers&lt;/h2&gt;
&lt;p&gt;WinUI developers using VS Code, Rider, or command-line tooling have been underserved. The existing Visual Studio templates weren&amp;rsquo;t usable outside of VS — you had to manually recreate project structure and wire up the basics.&lt;/p&gt;
&lt;p&gt;These templates are open source (see &lt;a href="https://github.com/microsoft/WindowsAppSDK/pull/6407"&gt;WindowsAppSDK PR #6407&lt;/a&gt;), developed from &lt;a href="https://github.com/microsoft/microsoft-ui-xaml/issues/10388"&gt;community feedback&lt;/a&gt;, and available now. Visual Studio support is in progress — these same templates will eventually work there too.&lt;/p&gt;
&lt;p&gt;For teams that want to script their WinUI project setup, integrate it into CI, or just use an editor other than Visual Studio, this is a meaningful improvement.&lt;/p&gt;
&lt;p&gt;Original post: &lt;a href="https://devblogs.microsoft.com/ifdef-windows/introducing-dotnet-new-templates-for-winui/"&gt;Introducing dotnet new WinUI templates&lt;/a&gt;&lt;/p&gt;</content:encoded></item></channel></rss>