{"id":1063,"date":"2026-05-04T16:19:17","date_gmt":"2026-05-04T23:19:17","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/?p=1063"},"modified":"2026-05-04T16:19:17","modified_gmt":"2026-05-04T23:19:17","slug":"announcing-the-winapp-vs-code-extension-run-debug-and-package-windows-apps-in-vs-code","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/ifdef-windows\/announcing-the-winapp-vs-code-extension-run-debug-and-package-windows-apps-in-vs-code\/","title":{"rendered":"Announcing the WinApp VS Code Extension \u2014 Run, Debug, and Package Windows Apps in VS Code"},"content":{"rendered":"

\"decorative<\/a><\/p>\n

VS Code is where many cross-platform and web developers already work, but getting package identity, MSIX packaging, and Windows SDK tooling often meant reaching for Visual Studio or command-line tools. The WinApp VS Code extension<\/strong>\u00a0brings the full power of the Windows App Development CLI<\/a> directly into VS Code. Via the extension, you can initialize, run, debug, package, and sign Windows applications from a variety of development frameworks without ever leaving the editor.<\/p>\n

Whether you’re building with .NET, WPF, WinUI, C++, Electron, Rust, Tauri, or Flutter,<\/strong>\u00a0this extension can help you streamline your Windows development process.<\/p>\n

\"Screenshot<\/a><\/p>\n

Ready to get started? The WinApp VS Code extension<\/strong> is now available in public preview on the Visual Studio Code Marketplace<\/a>.<\/p>\n

Let’s walk through what’s included.<\/p>\n

\ud83d\udc1b Integrated Launching and Debugging with Package Identity<\/h2>\n

Many Windows APIs \u2014 notifications, background tasks, on-device AI, share targets \u2014 require your app to have package identity<\/strong>. Traditionally, getting identity meant building a full MSIX installer or running from Visual Studio. With the WinApp extension, you can run Windows apps with package identity without having to leave VS Code.<\/p>\n

The extension provides a custom winapp<\/code> debug type<\/strong> that gives your app package identity, launches your app, and attaches your debugger, all from a single F5<\/strong>\u00a0press.<\/p>\n

\"Launch<\/a><\/p>\n

How it works:<\/strong><\/p>\n

After the user presses F5<\/strong>\u00a0to start a debug session, the extension:<\/p>\n

    \n
  1. Locates your build output and manifest<\/li>\n
  2. Launches your app via winapp run<\/code> to give it package identity<\/li>\n
  3. Attaches a child debug session using your preferred debugger<\/li>\n<\/ol>\n

    Supported debuggers:<\/strong><\/p>\n\n\n\n\n\n\n
    debuggerType<\/code><\/td>\nLanguage<\/td>\nRequired Extension<\/td>\n<\/tr>\n
    coreclr<\/code> (default)<\/td>\nC# \/ .NET<\/td>\nC# Dev Kit<\/a><\/td>\n<\/tr>\n
    cppvsdbg<\/code><\/td>\nC \/ C++<\/td>\nC\/C++<\/a><\/td>\n<\/tr>\n
    node<\/code><\/td>\nNode.js \/ Electron<\/td>\nBuilt-in<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Getting started is as simple as adding a winapp<\/code> configuration to your launch.json<\/code>:<\/p>\n

    {\r\n  \"version\": \"0.2.0\",\r\n  \"configurations\": [\r\n    {\r\n      \"type\": \"winapp\",\r\n      \"request\": \"launch\",\r\n      \"name\": \"WinApp: Launch and Attach\"\r\n    }\r\n  ]\r\n}<\/code><\/pre>\n
    Automate the build step<\/h3>\n
    The winapp<\/code> debug type assumes your project has already been built. It does not<\/strong>\u00a0build automatically. After making code changes, you need to rebuild before pressing F5.<\/p>\n
    The good news: you can automate this with a preLaunchTask<\/code>\u00a0so your project is always built before every debug session.<\/p>\n
    1. Define a build task<\/strong> in .vscode\/tasks.json<\/code>\u00a0(example for .NET):<\/p>\n
    {\r\n  \"version\": \"2.0.0\",\r\n  \"tasks\": [\r\n    {\r\n      \"label\": \"build\",\r\n      \"command\": \"dotnet\",\r\n      \"type\": \"process\",\r\n      \"args\": [\"build\", \"${workspaceFolder}\"],\r\n      \"problemMatcher\": \"$msCompile\"\r\n    }\r\n  ]\r\n}<\/code><\/pre>\n
    2. Reference it<\/strong> in your launch.json<\/code>:<\/p>\n
    {\r\n  \"type\": \"winapp\",\r\n  \"request\": \"launch\",\r\n  \"name\": \"WinApp: Launch and Attach\",\r\n  \"preLaunchTask\": \"build\"\r\n}<\/code><\/pre>\n
    Now every time you press F5, VS Code will build your project first, then launch it with package identity and attach the debugger, just like the full Visual Studio experience.<\/p>\n
    See the full Debugging Guide<\/a>\u00a0for more details.<\/p>\n
    \ud83c\udfa8 Command Palette Commands<\/h2>\n
    Many of the WinApp CLI commands are available from the VS Code Command Palette (Ctrl+Shift+P<\/code>). Type WinApp <\/strong>and you’ll see the full list:<\/p>\n