...
| Child pages (Children Display) |
|---|
Creating a PowerPack
Creating a PowerPack is straight forward, as it starts by right-clicking Application and Packages in the root point of your installation and then clicking on Create PowerPack…
...
Fill in the Package Name and optionally set a Package Version and a Description. The Display name automatically follows a concatenation of name and version. You can edit the Display Name manually if you want to. When you’re done, click Create.
...
The newly created PowerPack is then created, and is visible inside the CI Console. In the same way that CapaPacks differ from native packs by the blue color, PowerPacks are shown with a green package icon.
...
Setting an Editor for PowerShell
When editing PowerShell scripts, you can use a different editor than you would normally use for other (.vbs) scripts. To set it up, click Tools => Options…
...
-and select the General Tab on the left side.
...
The Native Integrated Scripting Editor (ise) for PowerShell is powershell_ise.exe. The full path is; %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell_ise.exe.
Editing scripts
When editing installation scripts for VBScript based packages, the default editor is launched with the full path of the script, which is located inside the Package in the Scripts folder., like this;
...