PowerShell CmdLet as Visual Studio External Tool

Question

I am attempting to add a PowerShell cmdlet as an external tool in Visual Studio 2010, but whenever I call the external tool I get:

{foo} cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.

I have already set my system's execution policy to 'RemoteSigned' (I also tried 'Bypass'), so why is this happening? I am fully able to run that same script if I open up a command line and call it via powershell.exe path\to\script.ps1 (which is exactly what my external tool definition is calling).

Keith Hill · Accepted Answer · 2010-10-21 02:22:04Z

15

Are you running on a x64 system? If so, you have to set the execution for both x86 and x64 PowerShell. You can also pass the ExecutionPolicy directly as a parameter to Powershell (2.0) via the command line:

powershell.exe -ExecutionPolicy RemoteSigned -Command "&{ foo }"

edited Oct 21, 2010 at 2:22

answered Oct 21, 2010 at 0:26

Keith Hill

204k44 gold badges370 silver badges377 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Antony Scott Over a year ago

Nice one. You helped me out of a hole there :)

Collectives™ on Stack Overflow

PowerShell CmdLet as Visual Studio External Tool

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related