See the version list below for details.
Install-Package forceps -Version 126.96.36.199
dotnet add package forceps --version 188.8.131.52
<PackageReference Include="forceps" Version="184.108.40.206" />
paket add forceps --version 220.127.116.11
#r "nuget: forceps, 18.104.22.168"
// Install forceps as a Cake Addin #addin nuget:?package=forceps&version=22.214.171.124 // Install forceps as a Cake Tool #tool nuget:?package=forceps&version=126.96.36.199
ForcePS - Allows you to run a PowerShell script from the Command Prompt bypassing Windows PowerShell Script Execution Policy.
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.
USAGE: ForcePS PSscript.ps1 parameter1 parameter2
This package has no dependencies.
This package is not used by any NuGet packages.
This package is not used by any popular GitHub repositories.
* v188.8.131.52 - updated donation link :)
* v1.0 - initial release