Start here if you want to work on the project.
README.mdfor the project overview and installation notesdocs/DEVELOPMENT.mdfor build and debug flowdocs/PUBLISHING.mdfor packaging and release flowdocs/TROUBLESHOOTING.mdfor common issues
- Keep changes small and focused.
- Preserve manifest / CLSID consistency between
UnityExtension.csandPackage.appxmanifest. - Keep code trim-safe and AOT-compatible.
- Treat CsWinRT / Windows SDK projection warnings (
IL2081/IL2104) as non-fatal unless runtime issue proves otherwise. Local publish defaults suppress; useSuppressSdkNoise=falseonly for trim review. - Avoid reflection-heavy patterns unless the upstream SDK requires them.
- Do not hardcode package versions in project files if centralized package management is used.
- Make your change.
- Build locally.
- Test in PowerToys.
- Verify publish behavior if the change affects deployment.
- Check trimming, nullable, and packaging diagnostics.
- Describe what changed and why.
- Mention any packaging or debug impact.
- Include manual validation notes when relevant.
Use the latest Microsoft Learn / PowerToys docs for Command Palette, packaging, publishing, and debugging.