Merge VS Code Extension into main (#420)

## Description

<!-- Briefly describe what this PR does and why -->
Merge VS Code extension into main. Includes Winapp commands, launch and
debug, and README. Does not include extension in publish.

Adds WinUI templates.

## Usage Example

<!-- If this PR adds or changes commands, flags, or APIs, include a
short code snippet -->
<!-- Example:
```bash
winapp store app list
```
-->
Install extension in VS Code and use commands/launch windows apps. 

## Related Issue

<!-- Link to any related issues: Fixes #123, Closes #456, Related to
#789 -->

## Type of Change

<!-- Keep the applicable line(s), delete the rest -->

- ✨ New feature

## Checklist
<!-- Delete the ones that do not apply to your changes -->

- [ ] New tests added for new functionality (if applicable)
- [x] Tested locally on Windows
- [ ] Main [README.md](../README.md) updated (if applicable)
- [ ] [docs/usage.md](../docs/usage.md) updated (if CLI commands
changed)

## Screenshots / Demo

<!-- If applicable, add screenshots or GIFs demonstrating the changes
-->

## Additional Notes

<!-- Any additional information that reviewers should know -->

## AI Description

<!-- ai-description-start -->
This pull request merges the VS Code extension into the main codebase,
introducing Winapp commands, launch, and debug features. Additionally,
it adds WinUI templates and includes updated documentation reflecting
these changes. Users can now install the extension and utilize commands
for launching Windows apps directly from VS Code.

```bash
# Add alias inferred from the Executable attribute in the manifest
winapp manifest add-alias

# Specify the alias name explicitly
winapp manifest add-alias --name myapp

# Target a specific manifest file
winapp manifest add-alias --manifest ./path/to/appxmanifest.xml
```
<!-- ai-description-end -->

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Alexandre Zollinger Chohfi <alzollin@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Nikola Metulev <nmetulev@users.noreply.github.com>
Co-authored-by: Nikola Metulev <711864+nmetulev@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Zach Teutsch <88554871+zateutsch@users.noreply.github.com>

Author: 8 people

.github/plugin/agents/winapp.agent.md

@@ -226,7 +226,7 @@ Want to inspect or interact with a running app's UI?
 
 ### .NET (WPF, WinForms, Console)
 - **Setup:** `winapp init --use-defaults` — but if you already have a `Package.appxmanifest` (e.g., WinUI 3 apps), you likely **don't need `winapp init`**. Just ensure your `.csproj` references the `Microsoft.WindowsAppSDK` NuGet package and has the right properties for packaged builds.
-- **Run with identity:** Build with `dotnet build <project.csproj> -c Debug -p:Platform=x64`, then `winapp run bin\x64\Debug\<tfm>\win-x64\`. Replace `<tfm>` with your target framework (e.g., `net10.0-windows10.0.26100.0`) and adjust architecture as needed.
+- **Run with identity:** `winapp init` auto-adds the `Microsoft.Windows.SDK.BuildTools.WinApp` NuGet package, so just `dotnet run` registers a loose layout package and launches with identity. Without the NuGet package, build with `dotnet build <project.csproj> -c Debug -p:Platform=x64`, then `winapp run bin\x64\Debug\<tfm>\win-x64\`. Replace `<tfm>` with your target framework (e.g., `net10.0-windows10.0.26100.0`) and adjust architecture as needed.
 - **Package:** `dotnet build -c Release -p:Platform=x64`, then `winapp package bin\x64\Release\<tfm>\win-x64\ --cert devcert.pfx`
 - No native addons needed — .NET has direct Windows API access via `Microsoft.Windows.SDK.NET.Ref`
 - Guide: https://github.com/microsoft/WinAppCli/blob/main/docs/guides/dotnet.md

.github/plugin/skills/winapp-cli/frameworks/SKILL.md

@@ -50,6 +50,7 @@ Additional Electron guides:
 - Projects with NuGet references to `Microsoft.Windows.SDK.BuildTools` or `Microsoft.WindowsAppSDK` **don't need `winapp.yaml`** — winapp auto-detects SDK versions from the `.csproj`
 - The key prerequisite is `appxmanifest.xml`, not `winapp.yaml`
 - No native addon step needed — unlike Electron, .NET can call Windows APIs directly
+- `winapp init` automatically adds the `Microsoft.Windows.SDK.BuildTools.WinApp` NuGet package, enabling `dotnet run` with automatic identity registration
 
 **If you already have a `Package.appxmanifest`** (e.g., WinUI 3 apps or projects with an existing packaging setup), you likely **don't need `winapp init`** — your project is already configured for packaged builds. Just make sure:
 - Your `.csproj` references the `Microsoft.WindowsAppSDK` NuGet package (WinUI 3 apps already have this)

.github/plugin/skills/winapp-cli/manifest/SKILL.md

@@ -102,6 +102,23 @@ This adds a `uap5:AppExecutionAlias` extension to the manifest. If the alias alr
 
 > **When combined with `winapp run --with-alias`** or the `WinAppRunUseExecutionAlias` MSBuild property, this enables apps to run in the current terminal with inherited stdin/stdout/stderr instead of opening a new window.
 
+### Add an execution alias
+
+Execution aliases let users launch the app by typing its name in a terminal (e.g. `myapp`).
+
+```powershell
+# Add alias inferred from the Executable attribute in the manifest
+winapp manifest add-alias
+
+# Specify the alias name explicitly
+winapp manifest add-alias --name myapp
+
+# Target a specific manifest file
+winapp manifest add-alias --manifest ./path/to/appxmanifest.xml
+```
+
+This adds a `uap5:AppExecutionAlias` extension to the manifest. If the alias already exists, the command reports it and exits successfully.
+
 ## Manifest structure overview
 
 A typical `appxmanifest.xml` looks like:

.github/plugin/skills/winapp-cli/setup/SKILL.md

@@ -102,6 +102,7 @@ winapp run ./bin/Debug --debug-output
 
 Use `winapp run` during iterative development — it creates a loose layout package, registers a debug identity, and launches the app in one step. For identity-only registration without loose layout, use `winapp create-debug-identity` instead.
 
+
 #### Choosing between `run` and `create-debug-identity`
 
 | | `winapp run` | `create-debug-identity` |

.gitignore

@@ -155,6 +155,8 @@ obj/
 *.sln.docstates
 # VS Code
 .vscode/
+# Allow .vscode config for the VS Code extension project
+!src/winapp-VSC/.vscode/
 # Visual Studio
 .vs/
 # NuGet packages

.vscode/settings.json

@@ -77,5 +77,13 @@
         "xtr1common": "cpp",
         "xtree": "cpp",
         "xutility": "cpp"
-    }
+    },
+    "files.exclude": {
+		"src/winapp-VSC/out": false // set this to true to hide the "out" folder with the compiled JS files
+	},
+	"search.exclude": {
+		"src/winapp-VSC/out": true // set this to false to include "out" folder in search results
+	},
+	// Turn off tsc task auto detection since we have the necessary tasks as npm scripts
+	"typescript.tsc.autoDetect": "off"
 }

README.md

@@ -273,7 +273,7 @@ For more information see the [Code of Conduct FAQ](https://opensource.microsoft.
 
 To build the CLI:
 ```
-# Build the CLI and package for npm, and NuGet, from the repo root
+# Build the CLI and package for npm, VS Code extension, NuGet, and MSIX from the repo root
 .\scripts\build-cli.ps1
 ```
 

docs/dotnet-run-support.md

@@ -114,6 +114,7 @@ The main build script now includes NuGet packaging:
 ```powershell
 .\scripts\build-cli.ps1                        # Full build including NuGet
 .\scripts\build-cli.ps1 -SkipNuGet             # Skip NuGet packages
+.\scripts\build-cli.ps1 -SkipVsc              # Skip VS Code extension
 ```
 
 ## Usage
@@ -155,14 +156,15 @@ Register identity without launching:
 </PropertyGroup>
 ```
 
+
 Capture OutputDebugString messages and first-chance exceptions:
 ```xml
 <PropertyGroup>
   <WinAppRunDebugOutput>true</WinAppRunDebugOutput>
 </PropertyGroup>
 ```
 
-## Outstanding Production Blockers
+## Production Blockers
 
 ### 1. CLI AOT Build Issues (BLOCKING)
 

docs/fragments/skills/winapp-cli/frameworks.md

@@ -45,6 +45,7 @@ Additional Electron guides:
 - Projects with NuGet references to `Microsoft.Windows.SDK.BuildTools` or `Microsoft.WindowsAppSDK` **don't need `winapp.yaml`** — winapp auto-detects SDK versions from the `.csproj`
 - The key prerequisite is `appxmanifest.xml`, not `winapp.yaml`
 - No native addon step needed — unlike Electron, .NET can call Windows APIs directly
+- `winapp init` automatically adds the `Microsoft.Windows.SDK.BuildTools.WinApp` NuGet package, enabling `dotnet run` with automatic identity registration
 
 **If you already have a `Package.appxmanifest`** (e.g., WinUI 3 apps or projects with an existing packaging setup), you likely **don't need `winapp init`** — your project is already configured for packaged builds. Just make sure:
 - Your `.csproj` references the `Microsoft.WindowsAppSDK` NuGet package (WinUI 3 apps already have this)

docs/fragments/skills/winapp-cli/manifest.md

@@ -97,6 +97,23 @@ This adds a `uap5:AppExecutionAlias` extension to the manifest. If the alias alr
 
 > **When combined with `winapp run --with-alias`** or the `WinAppRunUseExecutionAlias` MSBuild property, this enables apps to run in the current terminal with inherited stdin/stdout/stderr instead of opening a new window.
 
+### Add an execution alias
+
+Execution aliases let users launch the app by typing its name in a terminal (e.g. `myapp`).
+
+```powershell
+# Add alias inferred from the Executable attribute in the manifest
+winapp manifest add-alias
+
+# Specify the alias name explicitly
+winapp manifest add-alias --name myapp
+
+# Target a specific manifest file
+winapp manifest add-alias --manifest ./path/to/appxmanifest.xml
+```
+
+This adds a `uap5:AppExecutionAlias` extension to the manifest. If the alias already exists, the command reports it and exits successfully.
+
 ## Manifest structure overview
 
 A typical `appxmanifest.xml` looks like: