PowerShell remote

[HippyCraig]

VB Version 8.7.0.1
PSExec 2.11

[kinook]

Please send or post the .bld file and log file.

[HippyCraig]

see attached, I removed the account info

[kinook]

What version+SP+bitness of Windows on the local machine and remote machine?

[HippyCraig]

Both are 2008 R2 Standard SP1

[kinook]

This is fixed in the latest build (VisBuildPro.exe 9.0.0.2 in Help | About after installing). There were two problems:

1) PowerShell didn't like the path to the temporary script specified as \\computer\c$\xyz.ps1 on the remote call -- this was changed to reference as C:\xyz.ps1 instead.

2) PowerShell doesn't exit when called remotely -- a 'None' option was added to the Input format field on the Options tab, which must be used for remote calls to PowerShell to avoid this (see here for details).

Also, you should be able to specify Remote Signed rather than Unrestricted for the Execution policy on the Options tab.

[HippyCraig]

I will give it a try. I have a custom action that I wrote in VS2010 FW 4.0, that I use in my scripts. If I update to Version 9, I want to update the custom action to VS2013, can I use FW 4.5.2 for my custom action with VB 9x?