Inclusion of Powershell modules in appref-ms packages

[twoscoopsofpig]

Summary of the new feature/enhancement

In order to use modern authentication with Exchange Online, there is a module in appref-ms format which checks for updated versions of the module before running. The module is not accessible with Import-Module in a regular Powershell console, but can be installed from the Hybrid tab under the Exchange Admin Center of Exchange Online, as described at https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell?view=exchange-ps

I have attempted to add the full path to the appref=ms package as a new profile in Windows Terminal, but receive an error about bad syntax in profiles.json. I assume this is due to the presence of backslashes in the path to the module. Moving the appreff package to a folder in my PATH doesn't seem to make any difference either.

Considering the consolidation goal of this project, it would be useful to include all forms of the Powershell console, regardless of packaging.

Thanks for your attention!

[zadjii-msft]

You'll need to make sure to properly escape the commandline in your profile:

{
  "commandline": "this\will\not\work",
  "commandline": "but\\this\\will"
}

See also #1090

[twoscoopsofpig]

That doesn't work either, much like adding the package to a folder in the PATH and calling it by the relative filepath didn't work. This is probably down to the appref-ms packaging, not what that package calls or how it gets called.

…

On Wed, Jul 3, 2019 at 8:25 AM Mike Griese ***@***.***> wrote: You'll need to make sure to properly escape the commandline in your profile: { "commandline": "this\will\not\work", "commandline": "but\\this\\will" } See also #1090 <#1090> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1785?email_source=notifications&email_token=ALSPBQT762QIVW72WNWCY6LP5SSF7A5CNFSM4H5BIJA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZENY7Y#issuecomment-508091519>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALSPBQTEUCLW2WOAXXWY6LDP5SSF7ANCNFSM4H5BIJAQ> .

[zadjii-msft]

Could you share the error you're seeing, and the profile? I'm also fairly sure that you can't try and execute things that in subdirectories of things in your %PATH%, the executable's directory needs to be on %PATH% itself.

[twoscoopsofpig]

It is directly in the path. The error is simply that the requested package won't open when I try to open it from the new tab dropdown or by hotkey - the new tab flashes on screen but never populates or stays on screen. I'm including my profile below. It does use a new GUID, though it reuses the original icon from the initial Powershell profile. { "acrylicOpacity" : 0.5, "background" : "#12456", "closeOnExit" : true, "colorScheme" : "Campbell", "commandline" : "C:\\Users\\conantb\\Documents\\Admin\\Microsoft Exchange Online Powershell Module.appref-ms", "cursorColor" : "#FFFFFF", "cursorShape" : "bar", "fontFace" : "Consolas", "fontSize" : 10, "guid" : "{dad46b19-2e01-41cf-b310-e4022c80dbb9}", "historySize" : 9001, "icon" : "ms-appx:///ProfileIcons/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png", "name" : "Windows EXOPS PowerShell", "padding" : "0, 0, 0, 0", "snapOnInput" : true, "startingDirectory" : "%USERPROFILE%", "useAcrylic" : false } Please also note that this profile is using the absolute path to the package, though even after adding C:\users\conantb\Documents\Admin to the path and referring to the package simply as "Microsoft Exchange Online Powershell Module.appref-ms" I still see the issue. Further, renaming the package and using that name fails in a similar manner. I've also confirmed that calling the package in the path works from the run box (among other methods).

…

On Wed, Jul 3, 2019 at 8:56 AM Mike Griese ***@***.***> wrote: Could you share the error you're seeing, and the profile? I'm also *fairly* sure that you can't try and execute things that in subdirectories of things in your %PATH%, the executable's directory needs to be on %PATH% itself. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1785?email_source=notifications&email_token=ALSPBQTST7HOELIEIX77T2TP5SVZPA5CNFSM4H5BIJA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZEQYDA#issuecomment-508103692>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALSPBQWN7KABIYRW2N2NC3LP5SVZPANCNFSM4H5BIJAQ> .

[zadjii-msft]

Maybe try

"\\\"C:\\Users\\conantb\\Documents\\Admin\\Microsoft Exchange Online Powershell Module.appref-ms\\\""

Escaping spaces is particularly tricky ATM.

[twoscoopsofpig]

Neither that nor nesting single quotes (escaped or otherwise) works.

When the appref package fires, it runs an updater and then loads the console with the module imported.

[DHowett-MSFT]

Ah, this is somewhat worrying. I'm not actually sure how appref-ms modules are supposed to be launched. Let me have a look -- if it's something we can solve with the right powershell command line, this'll turn into general user documentation and advice. If it's something that can't be solved with a command line, we'll need to start asking the hard questions.

[DHowett-MSFT]

This might just boil down to #492. It looks like appref-ms shortcuts are another type of ClickOnce application, which means their launch must be brokered through another process (internet explorer, windows shell, etc.) Right now, we can't support hooking the launch of another console application through a broker.

[twoscoopsofpig]

That rings true for me. Thanks for looking into it! Are there any plans on the roadmap to support this?

…

On Sun, Jul 7, 2019, 21:51 Dustin L. Howett (MSFT) ***@***.***> wrote: This might just boil down to #492 <#492>. It looks like appref-ms shortcuts are another type of ClickOnce application, which means their launch *must* be brokered through another process (internet explorer, windows shell, etc.) Right now, we can't support hooking the launch of another console application through a broker. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1785?email_source=notifications&email_token=ALSPBQRPUS37GNPT43BCYFLP6KTSBA5CNFSM4H5BIJA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZL2K7I#issuecomment-509060477>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALSPBQUQI5WMPVOCPRRUVPDP6KTSBANCNFSM4H5BIJAQ> .

[DHowett-MSFT]

Sure is. Please follow #492 😄

[twoscoopsofpig]

Much appreciated!

…

On Sun, Jul 7, 2019, 22:27 Dustin L. Howett (MSFT) ***@***.***> wrote: Sure is. Please follow #492 <#492> 😄 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1785?email_source=notifications&email_token=ALSPBQTE2QS7GHVL2OPSY6DP6KX3PA5CNFSM4H5BIJA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZL3U5Y#issuecomment-509065847>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALSPBQX4GISJ364WJQG5TVLP6KX3PANCNFSM4H5BIJAQ> .

[ghost]

This issue has been marked as duplicate and has not had any activity for 1 day. It will be closed for housekeeping purposes.