Info
| Version: | 1.0.0.2 |
| Author(s): | Bill Curran |
| Last Update: | Sunday, August 11, 2019 |
| .NET Fiddle: | Create the first Fiddle |
| Project Url: | https://github.com/bcurran3/ChocolateyPackages/blob/master/forceps |
| NuGet Url: | https://www.nuget.org/packages/forceps |
Install
Install-Package forceps
dotnet add package forceps
paket add forceps
forceps Download (Unzip the "nupkg" after downloading)
Dependencies
Tags
No more "File PSscript.ps1 cannot be loaded because running scripts is disabled on this system." messages!
"Laziness is the mother of invention."
I wrote ForcePS because I was lazy and didn't want to keep changing my Windows PowerShell Script Execution Policy back and forth to run scripts.
So I made a little one line batch file that would call PowerShell with the appropriate parameters to bypass the execution policy. Now I've added some error checking, compiled it, and have released it to the world for others who can't remember or don't want to have to type "Set-ExecutionPolicy Unrestricted" and "Set-ExecutionPolicy Restricted" repeatedly. Now you can just run ForcePS from the Command Prompt followed by the name of a PowerShell script and..Walah! The PS script will run without hassle, all without you having to change any settings.
Elevated Command Prompt required for some small sense of security.
SCREENSHOT:
https://cdn.staticaly.com/gh/bcurran3/ChocolateyPackages/master/forceps/ForcePS_screenshot.png
USAGE: ForcePS PSscript.ps1 parameter1 parameter2.