microsoft / microsoft/WindowsAppSDK

Improve documentation and getting started experience with VSCode and Windows App SDK

Open
#5,064 0 comments 0 reactions 0 assignees View on GitHub
documentation
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

### Describe the bug

A partner reported, We just started using it, it took about a week for me to figure out how to get it working with Electron, so that's my first piece of feedback: we use Visual Studio Code/Cursor and electron, and it was not trivial to figure out how to start using Windows App SDK, nor was it documented anywhere. The documentation is definitely skewed towards Visual Studio.

A quick search for VSCode and Windows App SDK only brings up StackOverflow results.

### Steps to reproduce the bug

Try to create a project using electro, VSCode, Cursor and Windows App SDK.

### Expected behavior

_No response_

### Screenshots

_No response_

### NuGet package version

None

### Packaging type

_No response_

### Windows version

_No response_

### IDE

Other

### Additional context

Interesting. Even the IDE drop downs are just VS.

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the existing Windows App SDK getting-started documentation and its Visual Studio-focused IDE guidance first. Reproduce the setup using Electron with VSCode or Cursor, then document the missing workflow and update any relevant IDE guidance so a newcomer can follow it successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, vscode
Domain
desktop-dev, developer-experience, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.