Bring "Open in Windows Terminal" for Right Click on Drive Letter
Description of the new feature/enhancement
Bring "Open in Windows Terminal" for right click on drive letter. In Windows Terminal 1.1.1671.0 I am able to do this on a folder but it does not work on a drive letter.
I'm not sure if this is caused by the same thing as #6414 or not.
I'm glad your tracking that issue as well (#6414). I was about report that.
No no, this is the exact same thing. /dup #6414
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
That should teach me to read. It probably isn't the same.
I'm now using version 1.6.10571.0 of Windows Terminal. There still is no right click on the drive letter to "Open in Windows Terminal". I can, however, right click on a white area in any folder and "Open in Windows Terminal" is available.
After reading this thread, I'm confused on whether this is a duplicate of another issue. When I searched around, I came right back to this one.
Heck, I think even Dustin is confused 😆

I think this is a unique enough issue. I'm not sure how we attach to the context menu for a drive (not just a folder), but there's gotta be a way.
Yep, there has to be a way. With a shift right click there is an "Open PowerShell window here" and on a regular right click there is an "Open with Code" item.
This is being tracked internally with MSFT:32135340 (I think?)
(It cannot be done with packaged COM today. Yeah.)
- MSFT:32135340 has the most notes but the following are also relevant:
- MSFT:35558552
- MSFT:36784232
Ah. So, I'll need to wait for the SV2 SDK to use this then presumably? I just tried adding this to the Terminal (built on the 22000 SDK) and it gave me the classic APPX0501 error.
<desktop5:ItemType Type="Drive"> <desktop5:Verb Id="OpenTerminalDev" Clsid="52065414-e077-47ec-a3ac-1cc5455e1b54" /> </desktop5:ItemType>Also, will this just gracefully continue to do nothing on Windows 10?
(I also just tried this with
desktop10:ItemTypebut got something aboutThe schema for MaxVersionTested specified does not recognize XML fields with namespace "http://schemas.microsoft.com/appx/manifest/desktop/windows10/10".)
right, I think it is available in the {SV2} SDK. I think one of them either Drive or DesktopBackground will just work in SV1. I'm not sure about what will happen on Windows 10.
Okay, so if we target the sv2 sdk, this might just work today, but we really really need to confirm on Windows 10 manually.
Ah. So, I'll need to wait for the SV2 SDK to use this then presumably? I just tried adding this to the Terminal (built on the 22000 SDK) and it gave me the classic APPX0501 error.
<desktop5:ItemType Type="Drive"> <desktop5:Verb Id="OpenTerminalDev" Clsid="52065414-e077-47ec-a3ac-1cc5455e1b54" /> </desktop5:ItemType>Also, will this just gracefully continue to do nothing on Windows 10? (I also just tried this with
desktop10:ItemTypebut got something aboutThe schema for MaxVersionTested specified does not recognize XML fields with namespace "http://schemas.microsoft.com/appx/manifest/desktop/windows10/10".)right, I think it is available in the {SV2} SDK. I think one of them either Drive or DesktopBackground will just work in SV1. I'm not sure about what will happen on Windows 10.
Okay, so if we target the sv2 sdk, this might just work today, but we really really need to confirm on Windows 10 manually.
What is sv2 sdk? does support Type="Drive" now? please tell me,thank you.
@nhchmg sv2 sdk in appx/msix packaging is Microsoft.Windows.SDK.BuildTools (Version 10.0.22621.*). Until now desktop10:ItemType is an undocumented property. We have tried to add it in M2Team/NanaZip#313 .
+1