IsePackV2

Hello, I know that the original question below was asked in 2014, but this is the first time I am seeing this add-on. StartAutomating mentioned that wee should set the execution policy as follows to have the add-on load without prompts:

Set-ExecutionPolicy Bypass -Force

however, due to the security issues presented with bypass, should the execution policy instead be:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy bypass -Force

so that you limit the security issues? Not trying to correct, so much as to understand. Just getting back into PowerShell scripting.

Thank you. 

I am getting below error while loading this module. Please guide me.

Exception calling "Add" with "3" argument(s): "The menu 'Search-Bing' uses shortcut 'Ctrl+B', which is already in use by the menu or editor functionality.
Parameter name: shortcut"
At C:\Users\mkum27\Documents\WindowsPowerShell\Modules\IsePackV2\Add-IseMenu.ps1:114 char:25
+ ...             $m = $iseMenu.Submenus.Add($itemName, $scriptBlock, $_.Sh ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentException
 

It seems as though this has replaced "Powershell Pack", but it's not clear to me from the Description whether the "Task Scheduler" module is still part of this code.

Thanks.

The install script InstallForAllUsers.cmd in IsePackV2.1.4.1 has the wrong format, i.e. all lines are concatenated to a single line which effectively renders the script non-functional because the first command is "echo".

This is the correct (multi-line) contents:
------------------------------------------
echo "Installing modules from %~dp0"
xcopy "%~dp0ShowUI" "%windir%\system32\WindowsPowerShell\v1.0\Modules\ShowUI" /y /s /i /d 
xcopy "%~dp0RoughDraft" "%windir%\system32\WindowsPowerShell\v1.0\Modules\RoughDraft" /y /s /i /d 
xcopy "%~dp0Pipeworks" "%windir%\system32\WindowsPowerShell\v1.0\Modules\Pipeworks" /y /s /i /d 
xcopy "%~dp0EZOut" "%windir%\system32\WindowsPowerShell\v1.0\Modules\EZOut" /y /s /i /d 
xcopy "%~dp0ScriptCop" "%windir%\system32\WindowsPowerShell\v1.0\Modules\ScriptCop" /y /s /i /d 
xcopy "%~dp0IsePackV2" "%windir%\system32\WindowsPowerShell\v1.0\Modules\IsePackV2" /y /s /i /d 

How do we load this pack by default? Adding the modules load to the profiles file brings up the security warning pop-up for each script to load - and there are many. Using the -Force parameter does not alleviate the problem. 

The pop-up for each script to load is because of your local execution policy.  It should be set to "Bypass", which will allow you to load scripts downloaded off the Internet.  You need to run this once as an administrator:

Set-ExecutionPolicy Bypass -Force

Then the module will load correctly.

If you want it to load each time, put the module into your ISE profile.  To do this, inside of the ISE, run:

psedit $profile

If that doesn't open a file, then run:

' '> $profile

Then put this line in the file:

Import-Module ISEPackV2


Hope this helps,

James