Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Windows 11 shell extension

Windows 11 shell extension

Scheduled Pinned Locked Moved The Lounge
tutorialquestioncomlinuxcryptography
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    Gary R Wheeler
    wrote on last edited by
    #1

    Disclaimer: This is not intended as a programming question. I'm looking for experience and/or references to resources. I tried asking this question in Q&A and wasn't successful posting it, as any keyword I specified was rejected. Before you condemn me for asking here, I have searched on both Microsoft Docs[^] and general Googling with little or no success. I have a Windows shell extension for an in-house diagnostic tool. Under Windows 11, the context menu entry it supplies is relegated to the "Show more options" submenu in Explorer. Naturally, I'd like to make my context menu entry a 1st class citizen. There is exactly one example that purports to demonstrate how to do this, and the comments indicate that it doesn't work. Microsoft's documentation isn't coherent on the subject. The gist of it seems to be that your application needs to be packaged like a UWP app, which requires a signing certificate and a whole lot of other bric-a-brac. By their own admission, VS2019 doesn't include the "tooling" to make this easy. Has anyone done this, or do they have any suggestions?

    Software Zen: delete this;

    L 2 Replies Last reply
    0
    • G Gary R Wheeler

      Disclaimer: This is not intended as a programming question. I'm looking for experience and/or references to resources. I tried asking this question in Q&A and wasn't successful posting it, as any keyword I specified was rejected. Before you condemn me for asking here, I have searched on both Microsoft Docs[^] and general Googling with little or no success. I have a Windows shell extension for an in-house diagnostic tool. Under Windows 11, the context menu entry it supplies is relegated to the "Show more options" submenu in Explorer. Naturally, I'd like to make my context menu entry a 1st class citizen. There is exactly one example that purports to demonstrate how to do this, and the comments indicate that it doesn't work. Microsoft's documentation isn't coherent on the subject. The gist of it seems to be that your application needs to be packaged like a UWP app, which requires a signing certificate and a whole lot of other bric-a-brac. By their own admission, VS2019 doesn't include the "tooling" to make this easy. Has anyone done this, or do they have any suggestions?

      Software Zen: delete this;

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      The steps you need to take are here: Grant identity to non-packaged desktop apps[^] There isn't a way to bypass the requirements if that's what you are asking.

      1 Reply Last reply
      0
      • G Gary R Wheeler

        Disclaimer: This is not intended as a programming question. I'm looking for experience and/or references to resources. I tried asking this question in Q&A and wasn't successful posting it, as any keyword I specified was rejected. Before you condemn me for asking here, I have searched on both Microsoft Docs[^] and general Googling with little or no success. I have a Windows shell extension for an in-house diagnostic tool. Under Windows 11, the context menu entry it supplies is relegated to the "Show more options" submenu in Explorer. Naturally, I'd like to make my context menu entry a 1st class citizen. There is exactly one example that purports to demonstrate how to do this, and the comments indicate that it doesn't work. Microsoft's documentation isn't coherent on the subject. The gist of it seems to be that your application needs to be packaged like a UWP app, which requires a signing certificate and a whole lot of other bric-a-brac. By their own admission, VS2019 doesn't include the "tooling" to make this easy. Has anyone done this, or do they have any suggestions?

        Software Zen: delete this;

        L Offline
        L Offline
        Lost User
        wrote on last edited by
        #3

        Gary R. Wheeler wrote:

        By their own admission, VS2019 doesn't include the "tooling" to make this easy

        As long as you have the current Windows SDK[^]. Everything you need is in there... including MakeAppx and SignTool.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups