microsoft / microsoft/WinAppVSCE

Consolidate XAML server publish and payload validation

Open
#165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement language-server
Dominant language
TypeScript
Stars
13
Forks
4
Avg merge
6d 1h
Merged PRs (30d)
11

Description

Is your feature request related to a problem? Please describe.

PR #50 introduced self-contained XAML server delivery. The ARM64 CI job currently repeats the canonical publish commands, and required runtime payload filenames are repeated in the bundle helper, VSIX validator, and delivery tests. These copies can drift as the runtime payload changes.

Describe the solution you'd like

Add a single-RID option to the canonical server bundle helper and move the RID/required-file definitions into one shared manifest consumable by Node and PowerShell validation paths. Use the helper from the ARM64 smoke job.

Additional context

This is follow-up refactoring from the final PR review. Current delivery and validation are functionally covered and passing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the canonical server bundle helper, the ARM64 smoke job, and the bundle helper, VSIX validator, and delivery tests mentioned in the issue. Trace how each currently defines the RID and required payload files, then identify how a shared manifest can be consumed by both Node and PowerShell paths. Done means the ARM64 job uses the helper and validation definitions have one source of truth without changing the passing delivery behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, powershell, typescript
Domain
build-system, ci-cd, testing, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.