Files
networkSetup/docs/code-design/examples/exe.1.0.0.isver
T
jychoi4andClaude Opus 5.5 366c8fe173 feat: add EXE projects with versioned install configuration
- EXE project kind next to MSIX: formats.exe, new EXE projects, EXE app
  info (architecture, UpgradeCode), per-kind workspace; EXE builds and
  signing are still refused explicitly (#9).
- Install configuration tabs: registry grid, shortcuts and installer
  properties with formatted-text checks (#10).
- Per-version .isver files: version list, add dialog, lock/unlock,
  delete with .isver.bak backups, description (#11).
- Major/patch versions with cumulative patch checks and automatic kind
  selection (#12).
- 설치화면 tab: setup steps, theme and scripts per version (#13).
- Preferences: theme and display language (#14).
- 설치파일 tab as an Explorer-style tree: per-row add/remove, Windows
  folder install locations (FileRule.targetRoot), picked files placed
  with FileRule.sourceFolder, unsaved-rule file preview (#17).

Checks: cargo fmt/clippy/test, 82 frontend tests, Vite build and the
msix-studio build pass. npm ci, GUI click tests and real EXE builds were
not run.

Refs #9 #10 #11 #12 #13 #14 #17

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 11:10:00 +09:00

21 lines
335 B
Plaintext

{
"version": "1.0.0",
"productCode": null,
"updateType": "major",
"locked": false,
"files": [
{
"id": "application",
"source": "appPayload",
"include": [
"**/*"
],
"exclude": [],
"targetRelativePath": "",
"required": true
}
],
"registry": [],
"shortcuts": []
}