- 18 Aug, 2014 1 commit
-
-
$powershell path is set to "C:\powershell" at line 27. This is fine, but on line 82 $powershellpath is called as ".$powershellpath\$filename". Because the path at line 27 is absolute, a period preceding the $powershellpath is not required at 82. It actually causes an error: Start-Process : This command cannot be executed due to the error: Unknown error (0x80041002). At C:\users\Nathan Sosnovske\Documents\ps2to3.ps1:81 char:14 Start-Process <<<< -FilePath ".$powershellpath\$filename" -ArgumentList /quiet CategoryInfo : InvalidOperation: (:) [Start-Process], InvalidOperationException FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand Removing the period on line 82 before $powershellpath fixes this error.
nathansoz committed
-
- 19 Jun, 2014 19 commits
-
-
Matt Martz committed
-
Chris Church committed
-
Chris Church committed
-
Must wait in order for script to be available
Don Schenck committed -
Debugging
Don Schenck committed -
Fixed
Don Schenck committed -
Using Start-Process
Don Schenck committed -
Chris Church committed
-
Paul Durivage committed
-
Don Schenck committed
-
Craig Ackerman committed
-
Craig Ackerman committed
-
Paul Durivage committed
-
Michael DeHaan committed
-
Michael DeHaan committed
-
Michael DeHaan committed
-
UpgradeToPS3.ps1 failed when tested with Ansible. Added logging output to file C:\powershell\install.log.
Don Schenck committed -
assumed.
Don Schenck committed -
Will install PowerShell 3 if the machine has a lower version. WILL NOT do anything if PowerShell 3 (or higher) is already installed.
Don Schenck committed
-