Skip to content

Conversation

@chatasweetie
Copy link
Contributor

I've fleshed out the guide of publishing to Store & WinGet for the first submission. It is still missing the automation of updates (not NEEDED but would be nice).

TODO for this PR:

  • Someone to review these steps to validate

@prmerger-automator
Copy link
Contributor

@chatasweetie : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 79e4a30:

⚠️ Validation status: warnings

File Status Preview URL Details
hub/powertoys/command-palette/publish-extension.md ⚠️Warning Details

hub/powertoys/command-palette/publish-extension.md

  • Line 45, Column 3: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/windows/apps/publish/partner-center/partner-center-developer-account' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 46, Column 68: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/windows/apps/design/style/iconography/visual-studio-asset-generation' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 37, Column 250: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/windows/apps/publish/' will be broken in isolated environments. Replace with a relative link.
  • Line 45, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/windows/apps/publish/partner-center/partner-center-developer-account' will be broken in isolated environments. Replace with a relative link.
  • Line 46, Column 68: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/windows/apps/design/style/iconography/visual-studio-asset-generation' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Copy link
Contributor

@alvinashcraft alvinashcraft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some fixes to address the build warnings. I'll take a closer look at the contents of the tutorial tomorrow. Thanks for updating this!

@chatasweetie
Copy link
Contributor Author

Thanks @alvinashcraft Before you do, Zach is going to walk through it to make sure it's not missing anything

Copy link

@zateutsch zateutsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Microsoft store comments

…card and point microsoft store expected naming, updated $projectFile file path to be one repo lower due to single extension different structure than my multi extension
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit a3a9da7:

⚠️ Validation status: warnings

File Status Preview URL Details
hub/powertoys/command-palette/publish-extension.md ⚠️Warning Details
uwp/index.yml ⚠️Warning Details

hub/powertoys/command-palette/publish-extension.md

  • Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
  • Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

uwp/index.yml

  • Line 12, Column 18: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.subservice': 'uwp-conceptual-docs' is not valid with 'ms.service' value 'uwp'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@chatasweetie
Copy link
Contributor Author

@zadjii-msft
Here is the draft of publishing extensions

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit c2b1618:

⚠️ Validation status: warnings

File Status Preview URL Details
hub/powertoys/command-palette/publish-extension.md ⚠️Warning Details

hub/powertoys/command-palette/publish-extension.md

  • Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
  • Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

davidegiacometti pushed a commit to davidegiacometti/windows-dev-docs that referenced this pull request Nov 3, 2025
* WinAppSDK 1.8 Preview 1 - Release Notes

WinAppSDK 1.8 Preview 1 - Release Notes

* Update preview-channel.md

* Update preview-channel-1.7.md

* Update preview-channel-1.7.md

* rename

* Updates

* Update preview-channel.md

* Update release-channels.md

* Update downloads.md

---------

Co-authored-by: KB <[email protected]>
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit d9d9ce2:

⚠️ Validation status: warnings

File Status Preview URL Details
hub/powertoys/command-palette/publish-extension.md ⚠️Warning Details

hub/powertoys/command-palette/publish-extension.md

  • Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
  • Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 4411cc7:

⚠️ Validation status: warnings

File Status Preview URL Details
hub/powertoys/command-palette/publish-extension.md ⚠️Warning Details

hub/powertoys/command-palette/publish-extension.md

  • Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
  • Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Copy link
Contributor

@alvinashcraft alvinashcraft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ran the changes through the Learn Authoring Assistant. These are the style guide suggestions it gave.

Copy link
Contributor

@alvinashcraft alvinashcraft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ran the changes through the Learn Authoring Assistant. These are the style guide suggestions it gave.

### Prepare the extension

1. In your IDE, open `<ExtensionName>\Package.appxmanifest`.
1. Replace the values with the information you copied from Partner Center:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this what Visual Studio does when right-clicking on your project and clicking "Associcate with Store"?

If so, I'd push this flow as it's much easier to go through vs manually copying stuff?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things might have changed but when I chatted with Mike back in August he said not to use Visual Studio to build the MSIX files and to use a dot net command instead

@zadjii-msft is this still the case?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've only ever personally used the dotnet build tools. Maybe I just have CLI-brainrot 🤷

I haven't personally ever actually built something for the Store, so maybe that option works cleaner?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ack, gonna try it out building with visual studio and upload it to store to see if it passes the msix checks

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tired building the msix using the "Package and Publish" → "Create App Packages" flow, but that wasn't listed as an option and I think it's because it doesn't have packaging (which when I look up, the internet suggest adding a "Windows Application Packaging Project". I think this is why when Mike & I tried building the MSIX we ended up using the CLI (and even with the CLI I still needed to add the store info to the project). I'm working on adding the missing content to the template as well as a script so the developer just runs the script, provides the store info and the script updates the .csproj & package.appxmanifest. If anyone else has done this I'm more than happy to get a VS -> Store publication

Copy link

@jiripolasek jiripolasek Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency on Microsoft.WindowsAppSDK.WinUI is the secret ingredient for that submenu appear :(

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh gawh! I added <PackageReference Include="Microsoft.WindowsAppSDK"> <PrivateAssets>all</PrivateAssets> </PackageReference> to my .csproj file and now I have the options 👀 I'll test it out, brb

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to add some context: microsoft/PowerToys#38530 (comment)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So yes, Create App Packages does appear with the added Windows App SDK dependency (Microsoft.WindowsAppSDK.WinUI), but since this runs inside of command palette isn't it going to be an issue?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

runs inside of command palette

At least for now, each extension is a separate process.


> [!NOTE]
> **MSIX packages explained**
> MSIX is Microsoft's modern app packaging format that provides secure installation, automatic updates, and clean uninstallation. It replaces older formats like MSI and ensures your extension integrates properly with Windows security and deployment features.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to MSIX docs-hub?

## Guide to WinGet publishing

<!--
Publishing to WinGet is the recommended distribution method for Command Palette extensions as it enables automatic discovery and installation directly within Command Palette. This guide covers the majority of the WinGet publication process, from preparing your project and creating build scripts to setting up GitHub Actions automation and submitting your first package manifest. You'll learn how to create installer packages, configure automated builds, and navigate the WinGet submission workflow to make your extension easily discoverable and installable for users.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it the recommended distribution method (long term)? @zadjii-msft ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Long term... no. Short term? Totally. We still don't have a LOS on store extensions directly in the palette itself

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have #41453, which currently promotes extensions from the MS Store. I haven’t gotten around to implementing #42216 yet :'(

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit dec9e9a:

⚠️ Validation status: warnings

File Status Preview URL Details
hub/powertoys/command-palette/publish-extension.md ⚠️Warning Details

hub/powertoys/command-palette/publish-extension.md

  • Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
  • Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@chatasweetie
Copy link
Contributor Author

Current status
there are 2 questions for @zadjii-msft:

  • to build MSIX for extension, can this be done via VS?
  • Is Winget the recommended distribution method (long term)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants