{"id":1525,"date":"2026-11-09T11:37:22","date_gmt":"2026-11-09T19:37:22","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/?p=1525"},"modified":"2026-11-09T11:37:22","modified_gmt":"2026-11-09T19:37:22","slug":"windows-app-development-cli-v0-8","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/windows-app-development-cli-v0-8\/","title":{"rendered":"Windows App Development CLI v0.8: WinUI DevTools Experimental Preview"},"content":{"rendered":"<p class=\"rich-composer-paragraph\"><a href=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/0.8-hero.webp\"><img decoding=\"async\" class=\"alignnone size-full wp-image-1526\" src=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/0.8-hero.webp\" alt=\"decorative hero image\" width=\"950\" height=\"514\" srcset=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/0.8-hero.webp 950w, https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/0.8-hero-300x162.webp 300w, https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/0.8-hero-768x416.webp 768w\" sizes=\"(max-width: 950px) 100vw, 950px\" \/><\/a><\/p>\n<p class=\"rich-composer-paragraph\">Windows App Development CLI (WinApp CLI) is a command-line tool for creating, running, debugging, and packaging Windows apps from your terminal or an AI coding agent.<\/p>\n<p class=\"rich-composer-paragraph\">Version 0.8.0 is here, and we&#8217;re excited to share the new features WinApp CLI has to offer. Here are the highlights:<\/p>\n<ul class=\"rich-composer-ul\">\n<li class=\"rich-composer-li\" value=\"1\"><b><strong class=\"rich-composer-bold\">WinUI DevTools (experimental preview):<\/strong><\/b> Pick an element, inspect its properties and layout, try a change live, leave a comment for your coding agent, or change app theme all from the live DevTools running alongside your app.<\/li>\n<li class=\"rich-composer-li\" value=\"2\"><b><strong class=\"rich-composer-bold\">Performance profiling:<\/strong><\/b> which can record WinUI activity and investigate expensive XAML parsing, layout, and rendering work from the terminal.<\/li>\n<li class=\"rich-composer-li\" value=\"3\"><b><strong class=\"rich-composer-bold\">C++ project support.<\/strong><\/b> Build and run a <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">.vcxproj<\/span><\/code>, or build and package it into an MSIX.<\/li>\n<\/ul>\n<p class=\"rich-composer-paragraph\">Update to the latest release with <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winget install Microsoft.WinAppCLI<\/span><\/code>, or visit <a class=\"rich-composer-link show-underlines-target\" href=\"https:\/\/github.com\/microsoft\/winappCli\/releases\">GitHub Releases<\/a> for release notes and downloads. For npm, run <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">npm install --save-dev @microsoft\/winappcli<\/span><\/code>.<\/p>\n<p class=\"rich-composer-paragraph\">Here&#8217;s an overview of what the new version has to offer.<\/p>\n<h2 class=\"rich-composer-h2\">\u26cf\ufe0fWinUI DevTools (Experimental Preview)<\/h2>\n<p class=\"rich-composer-paragraph\">With WinUI DevTools, you can inspect controls, experiment with property values, and leave feedback without leaving your running app.<\/p>\n<p class=\"rich-composer-paragraph\"><b><strong class=\"rich-composer-bold\">WinUI DevTools is in experimental preview.<\/strong><\/b> We&#8217;re actively developing the tools, fixing issues, and improving the experience. Features and behavior may change as we learn from your feedback.<\/p>\n<p class=\"rich-composer-paragraph\">To get started, run this from your WinUI project directory:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp run <span class=\"rich-composer-tok-default\">.<\/span><\/pre>\n<p class=\"rich-composer-paragraph\">Your app opens with a DevTools toolbar in a corner. Choose <b><strong class=\"rich-composer-bold\">Select element<\/strong><\/b>, then click a control. The DevTools window opens beside your app with the selected element, its place in the visual tree, and its properties, bindings, and layout.<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/intellisense-overview-Trim.gif\"><img decoding=\"async\" class=\"alignnone size-full wp-image-1532\" src=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/intellisense-overview-Trim.gif\" alt=\"winui app launched with devtools, user interacts with app and opens up devtools window to view property information for a control \" width=\"2066\" height=\"1066\" \/><\/a><\/p>\n<p class=\"rich-composer-paragraph\">DevTools supports WinUI 3 apps written in C# and C++. It starts by default for supported WinUI projects launched with <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp run<\/span><\/code>. It doesn&#8217;t start by default in CI or Windows Sandbox. To turn it off for a run, use <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp run . --devtools off<\/span><\/code>.<\/p>\n<h4 class=\"rich-composer-h3\">View your app&#8217;s Visual Tree<\/h4>\n<p class=\"rich-composer-paragraph\">The visual tree shows how the running UI is put together. Select <b><strong class=\"rich-composer-bold\">Just my XAML<\/strong><\/b> to keep the focus on elements you authored, rather than all the framework elements inside a control&#8217;s template. Click the text inside a button, for example, and DevTools selects the control from your XAML.<\/p>\n<p class=\"rich-composer-paragraph\">When DevTools can confirm an element against your project, it shows the XAML file and line where it&#8217;s declared. That gives you a path from &#8220;this is the thing I want to change&#8221; to the source that defines it, without searching for every matching label in the project.<\/p>\n<p class=\"rich-composer-paragraph\"><a href=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/visual-tree.webp\"><img decoding=\"async\" class=\"alignnone size-full wp-image-1528\" src=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/visual-tree.webp\" alt=\"visual tree shown in winapp devtools for a winui app\" width=\"1248\" height=\"1003\" srcset=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/visual-tree.webp 1248w, https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/visual-tree-300x241.webp 300w, https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/visual-tree-1024x823.webp 1024w, https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/visual-tree-768x617.webp 768w\" sizes=\"(max-width: 1248px) 100vw, 1248px\" \/><\/a><\/p>\n<h3 class=\"rich-composer-h3\">Test out property changes<\/h3>\n<p class=\"rich-composer-paragraph\">Expand a property in the inspector to edit its value and see the result in your running app. Try a different width, adjust spacing, or change a brush while keeping the surrounding UI in view.<\/p>\n<p class=\"rich-composer-paragraph\">The property pane also helps explain where the current value comes from. A value set on the element, supplied by a style, or resolved from a resource can lead you to different places in your source. For resource-backed properties, you can try <b><strong class=\"rich-composer-bold\">ThemeResource<\/strong><\/b> or <b><strong class=\"rich-composer-bold\">StaticResource<\/strong><\/b> references, with suggestions for compatible keys available to that element.<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/intellisense-overview-edit.gif\"><img decoding=\"async\" class=\"alignnone size-full wp-image-1533\" src=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/intellisense-overview-edit.gif\" alt=\"User edits margin property for a control using the winapp devtools properties panel\" width=\"2066\" height=\"1066\" \/><\/a><\/p>\n<p class=\"rich-composer-paragraph\">These edits are live experiments, not source edits. They disappear when the app restarts. Once you&#8217;ve found the value you want, update your app&#8217;s XAML and rebuild to keep it. Replacing a bound value can also replace the binding for that run, so treat an edit as an experiment rather than a permanent fix.<\/p>\n<h4 class=\"rich-composer-h3\">Leave comments for your coding agent<\/h4>\n<p class=\"rich-composer-paragraph\">Sometimes the fastest way to explain a change is to point at it.<\/p>\n<p class=\"rich-composer-paragraph\">Choose <b><strong class=\"rich-composer-bold\">Comments<\/strong><\/b> on the toolbar, click an element, and type a note such as &#8220;Change this label to Save changes&#8221;. Save it, and a marker stays on the element.<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/comments.gif\"><img decoding=\"async\" class=\"alignnone size-full wp-image-1535\" src=\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2026\/11\/comments.gif\" alt=\"user navigates to comments pane in winapp dev tools. User edits a comment for a control then resolves the comment in the pane\" width=\"2118\" height=\"1070\" \/><\/a><\/p>\n<p class=\"rich-composer-paragraph\">Your agent can then read the feedback:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp devtools comments list\r\nwinapp devtools comments get cmt_example<\/pre>\n<p class=\"rich-composer-paragraph\">Replace <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">cmt_example<\/span><\/code> with an ID from the list. A comment carries context about the selected element. The agent can check the source match, make the change, and mark the comment resolved:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp devtools comments update cmt_example <span class=\"rich-composer-tok-default\">--<\/span>status resolved <span class=\"rich-composer-tok-default\">--<\/span>note <span class=\"rich-composer-tok-string\">\"Updated the label\"<\/span><\/pre>\n<p class=\"rich-composer-paragraph\">Comments are saved with the project and can be read after the app closes.<\/p>\n<h4 class=\"rich-composer-h3\">Agent access to DevTools<\/h4>\n<p class=\"rich-composer-paragraph\">The <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp devtools<\/span><\/code> commands let you or your agent inspect the live tree, search for elements, read their source and properties, and try changes directly from your command-line:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp devtools inspect\r\nwinapp devtools search Save\r\nwinapp devtools <span class=\"rich-composer-tok-entity\">get-source<\/span> SaveButton\r\nwinapp devtools <span class=\"rich-composer-tok-entity\">get-property<\/span> SaveButton Width\r\nwinapp devtools <span class=\"rich-composer-tok-entity\">set-property<\/span> SaveButton Width 200<\/pre>\n<p class=\"rich-composer-paragraph\">Use the selector returned by inspection or a unique element name, and add <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">-a &lt;pid&gt;<\/span><\/code> when more than one app has DevTools. Add <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">--json<\/span><\/code> for structured output that a script or coding agent can work with.<\/p>\n<p class=\"rich-composer-paragraph\"><code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp devtools<\/span><\/code> complements <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp ui.<\/span><\/code> Use UI Automation to interact with an app as a user would, and use DevTools to look inside its WinUI elements, properties, and XAML.<\/p>\n<p class=\"rich-composer-paragraph\">See the <a class=\"rich-composer-link show-underlines-target\" href=\"https:\/\/github.com\/microsoft\/winappCli\/blob\/main\/docs\/guides\/devtools.md\">DevTools guide<\/a> for the full workflow, including headless operation. The <a class=\"rich-composer-link show-underlines-target\" href=\"https:\/\/github.com\/microsoft\/winappCli\/blob\/main\/docs\/guides\/devtools-advanced.md\">advanced guide<\/a> covers attaching to an existing app and explicitly enabling DevTools in Windows Sandbox.<\/p>\n<h2 class=\"rich-composer-h2\">\ud83d\udcc8Find expensive work with performance profiling<\/h2>\n<p class=\"rich-composer-paragraph\">When a page takes too long to open, you need to know where the time went. The new <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp perf<\/span><\/code> commands record WinUI activity through ETW, Windows&#8217; event tracing system, and turn it into reports you can query from the terminal.<\/p>\n<p class=\"rich-composer-paragraph\">Start a recording as you launch the project:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp run <span class=\"rich-composer-tok-default\">.<\/span> <span class=\"rich-composer-tok-default\">--<\/span>profile <span class=\"rich-composer-tok-default\">.<\/span>\\traces\\navigation <span class=\"rich-composer-tok-default\">--<\/span>detach<\/pre>\n<p class=\"rich-composer-paragraph\">Navigate through the scenario you want to investigate, then stop the recording with the capture ID returned by <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">run<\/span><\/code>:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp perf stop CAPTURE_ID\r\nwinapp perf analyze <span class=\"rich-composer-tok-default\">.<\/span>\\traces\\navigation<\/pre>\n<p class=\"rich-composer-paragraph\">The report includes process resource usage and observed UI-thread activity, with views for expensive XAML resources, layout operations, elements, and frame intervals. For .NET apps, recorded garbage-collection information can help you investigate overlap with a slow operation.<\/p>\n<p class=\"rich-composer-paragraph\">Drill into the evidence rather than treating every slow frame as the same problem:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp perf analyze <span class=\"rich-composer-tok-default\">.<\/span>\\traces\\navigation <span class=\"rich-composer-tok-default\">--<\/span>view parsing\r\nwinapp perf analyze <span class=\"rich-composer-tok-default\">.<\/span>\\traces\\navigation <span class=\"rich-composer-tok-default\">--<\/span>view hotspots <span class=\"rich-composer-tok-default\">--<\/span>min-frame-ms 16<span class=\"rich-composer-tok-default\">.<\/span>67<\/pre>\n<p class=\"rich-composer-paragraph\">By default, recording starts after launch and can miss early startup. Add <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">--profile-mode elevated<\/span><\/code> to record from launch; Windows asks for administrator approval for the recorder, while your app still runs under your normal account. Profiling is local-only, and its UI-thread timings aren&#8217;t measurements of GPU execution or displayed frame rate.<\/p>\n<p class=\"rich-composer-paragraph\">See the <a class=\"rich-composer-link show-underlines-target\" href=\"https:\/\/github.com\/microsoft\/winappCli\/blob\/main\/docs\/guides\/winui-performance.md\">WinUI performance guide<\/a> for recording limits, startup capture, and interpreting the results.<\/p>\n<h2 class=\"rich-composer-h2\">\u2699\ufe0fBuild, run, and package C++ projects<\/h2>\n<p class=\"rich-composer-paragraph\">The project workflow now includes Visual Studio C++ projects. Point <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp run<\/span><\/code> at a <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">.vcxproj<\/span><\/code>, and it builds with Visual Studio&#8217;s MSBuild before launching the app with package identity:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp run <span class=\"rich-composer-tok-default\">.<\/span>\\MyApp<span class=\"rich-composer-tok-default\">.<\/span>vcxproj<\/pre>\n<p class=\"rich-composer-paragraph\">You can also build and create an MSIX, the Windows app package format, directly from the project:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp package <span class=\"rich-composer-tok-default\">.<\/span>\\MyApp<span class=\"rich-composer-tok-default\">.<\/span>vcxproj <span class=\"rich-composer-tok-default\">--<\/span>cert <span class=\"rich-composer-tok-default\">.<\/span>\\devcert<span class=\"rich-composer-tok-default\">.<\/span>pfx<\/pre>\n<p class=\"rich-composer-paragraph\">The same command takes your C++ project from source to a signed package. You&#8217;ll need Visual Studio or its Build Tools with the C++ components required by your project, including the WinUI tools for a C++ WinUI app. See <a class=\"rich-composer-link show-underlines-target\" href=\"https:\/\/github.com\/microsoft\/winappCli\/blob\/main\/docs\/usage.md#c-projects-vcxproj\">C++ project support<\/a> for prerequisites and options.<\/p>\n<h2 class=\"rich-composer-h2\">\ud83c\udd94Run separate checkouts side by side<\/h2>\n<p class=\"rich-composer-paragraph\">Working on two branches of the same packaged app can mean one registration replaces the other. The new <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">--unique-identity<\/span><\/code> option gives each checkout its own package identity, the name Windows uses to distinguish installed packages:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp run <span class=\"rich-composer-tok-default\">.<\/span>\\checkout-a\\MyApp<span class=\"rich-composer-tok-default\">.<\/span>csproj <span class=\"rich-composer-tok-default\">--<\/span>unique-identity\r\nwinapp run <span class=\"rich-composer-tok-default\">.<\/span>\\checkout-b\\MyApp<span class=\"rich-composer-tok-default\">.<\/span>csproj <span class=\"rich-composer-tok-default\">--<\/span>unique-identity<\/pre>\n<p class=\"rich-composer-paragraph\">That lets you compare a change against another branch, or keep parallel coding-agent work from replacing the other checkout&#8217;s app registration. See <a class=\"rich-composer-link show-underlines-target\" href=\"https:\/\/github.com\/microsoft\/winappCli\/blob\/main\/docs\/usage.md#unique-identity-for-parallel-checkouts\">unique identity for parallel checkouts<\/a> for details.<\/p>\n<h2 class=\"rich-composer-h2\">\ud83d\udcf7Make recordings easier to follow<\/h2>\n<p class=\"rich-composer-paragraph\">UI recordings now include WinUI menus, flyouts, and tooltips. Add <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">--cursor<\/span><\/code> to show the mouse pointer and a short highlight for each click:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp ui record <span class=\"rich-composer-tok-default\">-<\/span>a MyApp <span class=\"rich-composer-tok-default\">--<\/span>cursor <span class=\"rich-composer-tok-default\">--<\/span>duration-sec 20 <span class=\"rich-composer-tok-default\">--<\/span>output <span class=\"rich-composer-tok-default\">.<\/span>\\demo<span class=\"rich-composer-tok-default\">.<\/span>mp4<\/pre>\n<p class=\"rich-composer-paragraph\">That makes a walkthrough easier to follow when the important action happens in a menu or depends on where someone clicked.<\/p>\n<p class=\"rich-composer-paragraph\">To keep the pointer visible without highlighting clicks, add <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">--no-click-highlight<\/span><\/code>:<\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winapp ui record <span class=\"rich-composer-tok-default\">-<\/span>a MyApp <span class=\"rich-composer-tok-default\">--<\/span>cursor <span class=\"rich-composer-tok-default\">--<\/span>no-click-highlight <span class=\"rich-composer-tok-default\">--<\/span>duration-sec 20 <span class=\"rich-composer-tok-default\">--<\/span>output <span class=\"rich-composer-tok-default\">.<\/span>\\demo-no-highlight<span class=\"rich-composer-tok-default\">.<\/span>mp4<\/pre>\n<h2 class=\"rich-composer-h2\">Other notable changes<\/h2>\n<ul class=\"rich-composer-ul\">\n<li class=\"rich-composer-li\" value=\"1\"><b><strong class=\"rich-composer-bold\">Better sample discovery<\/strong><\/b>: <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">find-ui<\/span><\/code> searches control descriptions and recognizes more ways to ask for controls, including table, data-grid, and spreadsheet queries.<\/li>\n<li class=\"rich-composer-li\" value=\"2\"><b><strong class=\"rich-composer-bold\">More precise UI actions<\/strong><\/b>: click and hover at explicit coordinates, scroll horizontally, and use type or class-name filters without a text query.<\/li>\n<\/ul>\n<h2 class=\"rich-composer-h2\">\ud83d\udc1bBug fixes<\/h2>\n<ul class=\"rich-composer-ul\">\n<li class=\"rich-composer-li\" value=\"1\">Fixed <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">winapp ui<\/span><\/code> hanging when inspecting WinUI 3 apps that contain a WebView2.<\/li>\n<li class=\"rich-composer-li\" value=\"2\">Fixed duplicate builds of referenced projects that could cause packaging failures.<\/li>\n<li class=\"rich-composer-li\" value=\"3\">Improved targeting and recovery guidance for minimized windows and hosted apps.<\/li>\n<li class=\"rich-composer-li\" value=\"4\">Fixed signing to use the hash algorithm a package was built with.<\/li>\n<li class=\"rich-composer-li\" value=\"5\">Fixed template selection when another installed template pack also uses the name <code spellcheck=\"false\"><span class=\"rich-composer-inline-code-text\">reactor<\/span><\/code>.<\/li>\n<\/ul>\n<h2 class=\"rich-composer-h2\">\ud83d\udd12Security and infrastructure<\/h2>\n<p class=\"rich-composer-paragraph\">This release also tightens DLL loading for the CLI and its diagnostic tools, updates cryptography dependencies, and adds benchmarks for agent-assisted app development and UI automation.<\/p>\n<h2 class=\"rich-composer-h2\">Get started today<\/h2>\n<p class=\"rich-composer-paragraph\">Try inspecting a control, leaving a comment, or profiling a slow page in your own project. Share what you find in the <a class=\"rich-composer-link show-underlines-target\" href=\"https:\/\/github.com\/microsoft\/winappCli\">GitHub repository<\/a>.<\/p>\n<p class=\"rich-composer-paragraph\"><b><strong class=\"rich-composer-bold\">Install via WinGet:<\/strong><\/b><\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">winget install Microsoft<span class=\"rich-composer-tok-default\">.<\/span>WinAppCLI<\/pre>\n<p class=\"rich-composer-paragraph\"><b><strong class=\"rich-composer-bold\">Install via npm:<\/strong><\/b><\/p>\n<pre class=\"rich-composer-code-block relative block overflow-x-auto whitespace-pre rounded-medium border border-muted bg-muted p-4 font-mono text-body-small\" spellcheck=\"false\" data-language=\"powershell\" data-highlight-language=\"powershell\">npm install <span class=\"rich-composer-tok-default\">--<\/span><span class=\"rich-composer-tok-entity\">save-dev<\/span> @microsoft\/winappcli<\/pre>\n<p class=\"rich-composer-paragraph\">Happy building!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Windows App Development CLI (WinApp CLI) is a command-line tool for creating, running, debugging, and packaging Windows apps from your terminal or an AI coding agent. Version 0.8.0 is here, and we&#8217;re excited to share the new features WinApp CLI has to offer. Here are the highlights: WinUI DevTools (experimental preview): Pick an element, inspect [&hellip;]<\/p>\n","protected":false},"author":110839,"featured_media":1526,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[4,79,10,61,92,91,49,72,73,8,78,6,7,15],"class_list":["post-1525","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ifdef-windows","tag-net","tag-cli","tag-desktop","tag-developer","tag-developer-tooling","tag-devtools","tag-dotnet","tag-winapp","tag-winappcli","tag-windows","tag-windows-apps","tag-winui","tag-winui3","tag-xaml"],"acf":[],"blog_post_summary":"<p>Windows App Development CLI (WinApp CLI) is a command-line tool for creating, running, debugging, and packaging Windows apps from your terminal or an AI coding agent. Version 0.8.0 is here, and we&#8217;re excited to share the new features WinApp CLI has to offer. Here are the highlights: WinUI DevTools (experimental preview): Pick an element, inspect [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/posts\/1525","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/users\/110839"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/comments?post=1525"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/posts\/1525\/revisions"}],"predecessor-version":[{"id":1538,"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/posts\/1525\/revisions\/1538"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/media\/1526"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/media?parent=1525"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/categories?post=1525"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-json\/wp\/v2\/tags?post=1525"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}