The extension was scaffolded from Microsoft's template, which leaves several placeholder/default values in the manifest and csproj. Before submitting to Partner Center or WinGet, these need to be cleaned up. Some changes can be made immediately; others require first registering in Partner Center to get your Publisher identity.
AdbExtension/Package.appxmanifest — all updated:
- Version:
1.0.0.1 - All display names:
ADB Extension for Command Palette - All descriptions:
Run ADB commands for connected Android devices directly from Command Palette.
Note:
Identity/Name,Identity/Publisher, andProperties/PublisherDisplayNameare left as scaffold defaults — fill in after Partner Center registration (Step 2).
Assets (AdbExtension/Assets/) — all 7 files are generic Microsoft template images. Replace with custom branding. Required files:
StoreLogo.pngSquare44x44Logo.scale-200.pngSquare44x44Logo.targetsize-24_altform-unplated.pngSquare150x150Logo.scale-200.pngWide310x150Logo.scale-200.pngSplashScreen.scale-200.pngLockScreenLogo.scale-200.png
- Register in Microsoft Partner Center → Apps and games → New Product → MSIX or PWA app.
- Reserve product name (e.g.
ADB Extension for Command Palette). - From Product Management → Product identity, copy:
Package/Identity/NamePackage/Identity/PublisherPackage/Properties/PublisherDisplayName
Update Package.appxmanifest with copied values:
<Identity
Name="<from Partner Center>"
Publisher="<from Partner Center>"
Version="1.0.0.1" />
<Properties>
<PublisherDisplayName><from Partner Center></PublisherDisplayName>
...
</Properties>Update AdbExtension.csproj — add to the first unconditional <PropertyGroup>:
<AppxPackageSigningEnabled>true</AppxPackageSigningEnabled>
<PackageCertificateThumbprint></PackageCertificateThumbprint>
<AppxBundle>Always</AppxBundle>
<AppxBundlePlatforms>x64|ARM64</AppxBundlePlatforms>cd AdbExtension\AdbExtension
dotnet build --configuration Release -p:GenerateAppxPackageOnBuild=true -p:Platform=x64 -p:AppxPackageDir="AppPackages\x64\"
dotnet build --configuration Release -p:GenerateAppxPackageOnBuild=true -p:Platform=ARM64 -p:AppxPackageDir="AppPackages\ARM64\"
makeappx bundle /v /d bin\Release\ /p AdbExtensionForCommandPalette_1.0.0.1_Bundle.msixbundle
Upload .msixbundle to Partner Center. In the Store description, note that reviewer needs PowerToys + Command Palette installed.
In AdbExtension/AdbExtension.csproj, in the first <PropertyGroup>:
- Remove:
<PublishProfile>win-$(Platform).pubxml</PublishProfile> - Add:
<WindowsPackageType>None</WindowsPackageType>
Create in AdbExtension/AdbExtension/:
setup-template.iss— Inno Setup installer config (use template from MS docs, fill in CLSIDd857a76b-60ad-4db5-a14c-22f1d4f7bfaaand app metadata)build-exe.ps1— PowerShell build script (setup .NET + Inno Setup → dotnet publish → create installer → upload)
Create .github/workflows/release-extension.yml — automates: build → package → create GitHub Release with x64 + ARM64 .exe assets.
After the GitHub Release is created:
wingetcreate new "<x64 .exe URL>" "<arm64 .exe URL>"
Follow prompts, add tag windows-commandpalette-extension to locale YAML files before submitting.
| File | Changes |
|---|---|
AdbExtension/Package.appxmanifest |
DisplayName, Description, Version, Publisher identity (post-Partner Center) |
AdbExtension/AdbExtension.csproj |
AppxPackage properties (post-Partner Center), WindowsPackageType swap for WinGet |
AdbExtension/Assets/*.png |
Replace all 7 with custom branding |
AdbExtension/AdbExtension/setup-template.iss |
Create new |
AdbExtension/AdbExtension/build-exe.ps1 |
Create new |
.github/workflows/release-extension.yml |
Create new |
- After Step 1: Deploy the MSIX and reload Command Palette — confirm display names are updated throughout
- After Step 3:
dir *.msixbundleconfirms bundle was created; upload to Partner Center submission - After Step 6: Trigger
gh workflow run release-extension.ymland confirm both.exeassets appear in the GitHub Release