How can we improve the Windows dev platform?

Allow context menu verbs with file explorer integration without having a file type association

On this page, there is explanation how to make a file explorer integration on a desktop bridge app:
https://msdn.microsoft.com/sv-se/windows/uwp/porting/desktop-to-uwp-extensions

In short you could add something like this in your manifest-file:

<uap3:Extension Category="windows.fileTypeAssociation">
<uap3:FileTypeAssociation Name="MyApp">
<uap:SupportedFileTypes>
<uap:FileType MultiSelectModel="Document">.txt</uap:FileType>
<uap:FileType>.foo</uap:FileType>
</uap:SupportedFileTypes>
<uap2:SupportedVerbs>
<uap3:Verb Id="Edit" Parameters="/e &quot;%1&quot;">Edit</uap3:Verb>
<uap3:Verb Id="Print" Parameters="/p &quot;%1&quot;">Print</uap3:Verb>
</uap2:SupportedVerbs>
<uap:Logo>Assets\MyExtensionLogo.png</uap:Logo>
</uap3:FileTypeAssociation>
</uap3:Extension>

I’m working on porting an app that could calculate MD5 checksums on a file. I want to add this as a context menu option on for instance zip and iso-files. But it’s not possible to do this without making a file type association as I get it :(. In my case I would also be happy if it was possible to add verbs on all file types, but this is something I could live without :).

Also, there is no way to having different verbs on different file types which could be quite limiting.

If I’m wrong I would love to be corrected :-).

15 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

pekspro shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base