Skip to content

Maintenance: re-extract vendored CmdPal SDK after Microsoft updates #29

Closed
Closed
Maintenance: re-extract vendored CmdPal SDK after Microsoft updates#29
Labels
documentationImprovements or additions to documentationneeds-infoWaiting on reporter for more information

Description

@nickknissen
nickknissen
opened on May 8, 2026

Why this exists

We vendor the CmdPal SDK in `tools/cmdpal-sdk/` to work around a NuGet/runtime WinRT IID mismatch. When Microsoft ships a new CmdPal version, the runtime IIDs change and our vendored SDK drifts — the extension stops loading.

Symptom

After a CmdPal upgrade, the extension fails to load (or silently no-ops). User sees nothing in the palette.

Procedure

See `tools/cmdpal-sdk/README.md` for the extraction steps.

Trigger

Open this issue (or close + reopen) any time Microsoft ships a CmdPal update, so the workaround stays current. Track in releases.

Long-term fix

Closes when the "Bump Microsoft.CommandPalette.Extensions NuGet" issue is resolved (the moment Microsoft publishes a NuGet package with matching runtime IIDs, we drop the vendored DLL entirely).

Activity

  1. nickknissen
    added
    documentationImprovements or additions to documentation
    on May 8, 2026

  2. nickknissen commented on May 20, 2026

    @nickknissen
    nickknissen
    on May 20, 2026
    OwnerAuthor

    This was generated by AI during triage.

    Triage Notes

    What we've established so far:

    • This is a maintenance/documentation task for the vendored Command Palette SDK workaround.
    • The repo currently vendors Microsoft.CommandPalette.Extensions.dll and .winmd under tools/cmdpal-sdk/ because the NuGet package can drift from the Command Palette runtime WinRT IIDs.
    • tools/cmdpal-sdk/README.md already documents the extraction command and the currently vendored source package/version.
    • The work should only be performed when a specific Microsoft Command Palette update has shipped or when extension loading is broken after an update.

    What we still need from you (@nickknissen):

    • Which Microsoft Command Palette package version should the vendored SDK be re-extracted from?
    • Has the extension currently stopped loading after a CmdPal update, or is this issue only a standing reminder for the next update?
    • If it is currently broken, what installed Microsoft.CommandPalette package version is present on the affected machine?
  3. nickknissen
    added
    needs-infoWaiting on reporter for more information
    on May 20, 2026

  4. nickknissen commented on Aug 18, 2026

    @nickknissen
    nickknissen
    on Aug 18, 2026
    OwnerAuthor

    Closing as obsolete. The workaround this issue existed to maintain is gone: #31 deleted tools/cmdpal-sdk/ and the project now references the Microsoft.CommandPalette.Extensions NuGet package directly, so there is no vendored SDK left to re-extract when Command Palette updates.

    The IID mismatch that motivated the vendoring turned out not to be real. What the override actually provided was Microsoft.CommandPalette.Extensions.winmd in the package, which the csproj now forces into the publish output.

  5. nickknissen
    closed this as completedon Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationneeds-infoWaiting on reporter for more information

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions