Replies: 3 comments 3 replies
-
It's probably not on the path. Have you tried An alternative might be to install pac using dotnet. When you do that, it automatically adds it to the path. |
Beta Was this translation helpful? Give feedback.
-
Microsoft.PowerApps.CLI nuget package is used purely as a zip file and compiled with full .net framework. If you need to use cross platform version compiled with .Net 6 then use Microsoft.PowerApps.CLI.Tool |
Beta Was this translation helpful? Give feedback.
-
@zhead13, @petrochuk,
When I run "dotnet tool list --global" or "dotnet tool list" is doesn't show any installed tools... |
Beta Was this translation helpful? Give feedback.
-
I'm trying to use the PowerApps CLI in an Azure Runbook running a Windows Hybrid Worker. The "pac" commands are recognised when directly on the Windows Server, but I cannot get them to be recognized in the Hybrid Runbook.
When I run Find-Package -Name "Microsoft.PowerApps.CLI" it finds it ok, but still fails on any pac commands:
pac : The term 'pac' is not recognized as the name of a cmdlet, function, script file, or operable program.
Do I need to import the package into Runbook session somehow, like you do with Modules?
Any help appreciated.
Beta Was this translation helpful? Give feedback.
All reactions