Template publication automation

.github/actions/spell-check/expect.txt

@@ -111,6 +111,7 @@ AUTORADIOBUTTON
 Autorun
 AUTOTICKS
 AUTOUPDATE
+autopf
 AValid
 AWAYMODE
 azcliversion
@@ -267,6 +268,8 @@ CONFIGW
 CONFLICTINGMODIFIERKEY
 CONFLICTINGMODIFIERSHORTCUT
 CONOUT
+Contoso
+coreclr
 constexpr
 contentdialog
 contentfiles
@@ -751,6 +754,7 @@ IFACEMETHOD
 IFACEMETHODIMP
 ifd
 IGNOREUNKNOWN
+ignoreversion
 IGo
 iid
 IIM
@@ -777,6 +781,7 @@ INITDIALOG
 INITGUID
 INITTOLOGFONTSTRUCT
 INLINEPREFIX
+Inno
 inlines
 Inno
 INPC
@@ -811,6 +816,7 @@ IPTC
 irow
 irprops
 isbi
+iscc
 isfinite
 iss
 issecret
@@ -1443,6 +1449,7 @@ RECTDESTINATION
 rectp
 RECTSOURCE
 recyclebin
+recursesubdirs
 Redist
 Reencode
 REFCLSID
@@ -1794,6 +1801,7 @@ TILEDWINDOW
 TILLSON
 timedate
 timediff
+timestamped
 timeunion
 timeutil
 TITLEBARINFO

src/modules/cmdpal/ExtensionTemplate/TemplateCmdPalExtension/TemplateCmdPalExtension/Package.appxmanifest

@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?>
+<?xml version="1.0" encoding="utf-8"?>
 
 <Package
   xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10"
@@ -8,13 +8,19 @@
   xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities"
   IgnorableNamespaces="uap uap3 rescap">
 
+  <!-- FOR PUBLISHING TO MICROSOFT STORE -->
+  <!-- When you're ready to publish your extension to Microsoft Store,you'll need to 
+    change the values in the Identity & Properties tags below
+      Name = replace with Microsoft Store's Package/Identity/Name 
+      Publisher = replace with Microsoft Store's Package/Identity/Publisher
+      DisplayName = replace with the reserved name from Partner Center
+      PublisherDisplayName = replace with Microsoft Store's Package/Properties/PublisherDisplayName
+      Logo = Confirm that this image exist at the path
+       -->
   <Identity
     Name="TemplateCmdPalExtension"
     Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
     Version="0.0.1.0" />
-  <!-- When you're ready to publish your extension, you'll need to change the
-       Publisher= to match your own identity -->
-
   <Properties>
     <DisplayName>TemplateDisplayName</DisplayName>
     <PublisherDisplayName>A Lone Developer</PublisherDisplayName>

src/modules/cmdpal/ExtensionTemplate/TemplateCmdPalExtension/TemplateCmdPalExtension/Publication/PublicationREADME.md

@@ -0,0 +1,129 @@
+# Publication Setup
+
+This folder contains tools to help you prepare your CmdPal extension for publication to the Microsoft Store and WinGet.
+
+## Files and Folders in this Directory
+
+### Scripts
+
+- **`one-time-store-publishing-setup.ps1`** - Configure your project for Microsoft Store publishing (run once)
+- **`build-msix-bundles.ps1`** - Build MSIX packages and create bundles for Store submission
+- **`one-time-winget-publishing-setup.ps1`** - Configure your project for WinGet publishing (run once)
+
+### Resource Folders
+
+- **`microsoft-store-resources/`** - Contains files used for Microsoft Store publishing:
+  - `bundle_mapping.txt` - Auto-generated file that maps MSIX files for bundle creation
+
+- **`winget-resources/`** - Contains templates and scripts for WinGet publishing:
+  - `build-exe.ps1` - Script to build standalone EXE installer
+  - `setup-template.iss` - Inno Setup installer template
+  - `release-extension.yml` - GitHub Actions workflow template (moved to `.github/workflows/` during setup)
+  - `Backups/` - Backup copies of configuration files (created during setup)
+
+## Microsoft Store Quick Start
+
+1. Open PowerShell and navigate to the Publication folder:
+
+   ```powershell
+   cd <YourProject>\Publication
+   ```
+
+2. Run the one-time setup script:
+
+   ```powershell
+   .\one-time-store-publishing-setup.ps1
+   ```
+
+3. Follow the prompts to enter your Microsoft Store information from Partner Center:
+   - Package Identity Name
+   - Publisher Certificate
+   - Display Name
+   - Publisher Display Name
+
+   The script will update your `Package.appxmanifest` with Store-specific values.
+
+4. Once configured, build your bundle:
+
+   ```powershell
+   .\build-msix-bundles.ps1
+   ```
+
+   This script will:
+   - Build x64 and ARM64 MSIX packages
+   - Automatically update `microsoft-store-resources\bundle_mapping.txt` with correct paths
+   - Create a combined MSIX bundle
+   - Display the bundle location when complete
+
+5. Upload the resulting `.msixbundle` file from `microsoft-store-resources\` to Partner Center
+
+## Troubleshooting
+
+### makeappx.exe not found
+
+The build script requires the Windows SDK. Install it via:
+
+- Visual Studio Installer (Individual Components → Windows SDK)
+- [Standalone Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk/)
+
+### Build errors
+
+Ensure you have:
+
+- .NET 9.0 SDK installed
+- Windows SDK 10.0.26100.0 or compatible version
+- No other instances of Visual Studio building the project
+
+### Bundle creation fails
+
+Check that:
+
+- Both x64 and ARM64 builds completed successfully
+- `microsoft-store-resources\bundle_mapping.txt` paths are correct (auto-updated by script)
+- No file locks on the MSIX files
+
+## WinGet Quick Start
+
+1. Open PowerShell and navigate to the Publication folder:
+
+   ```powershell
+   cd <YourProject>\Publication
+   ```
+
+2. Run the one-time setup script:
+
+   ```powershell
+   .\one-time-winget-publishing-setup.ps1
+   ```
+
+3. Follow the prompts to enter:
+   - GitHub Repository URL (where releases will be published)
+   - Developer/Publisher Name
+
+   The script will:
+   - Configure `winget-resources\build-exe.ps1` with your extension details
+   - Configure `winget-resources\setup-template.iss` with your extension information
+   - Move `release-extension.yml` to `.github\workflows\` in your repository root
+
+4. Commit and push changes to GitHub:
+
+   ```powershell
+   git add .
+   git commit -m "Configure extension for WinGet publishing"
+   git push
+   ```
+
+5. Trigger the GitHub Action to build and release:
+
+   ```powershell
+   gh workflow run release-extension.yml --ref main -f "release_notes=**First Release of <ExtensionName> Extension for Command Palette**
+
+   The inaugural release of the <ExtensionName> for Command Palette..."
+   ```
+
+   Or create a release manually through the GitHub web interface.
+
+## Additional Resources
+
+- [Command Palette Extension Publishing Documentation](https://learn.microsoft.com/en-us/windows/powertoys/command-palette/publish-extension)
+- [Microsoft Store Publishing Guide](https://learn.microsoft.com/windows/apps/publish/)