{"id":12037,"date":"2016-05-23T06:00:00","date_gmt":"2016-05-23T13:00:00","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=12037"},"modified":"2016-05-23T07:13:58","modified_gmt":"2016-05-23T14:13:58","slug":"add-custom-tools-to-the-menu","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2016\/05\/23\/add-custom-tools-to-the-menu\/","title":{"rendered":"Add custom tools to the menu"},"content":{"rendered":"

There are so many features in PowerShell Studio and PrimalScript that I think I can’t live without<\/a>, like the Format Script button, file groups<\/a>, and conditional breakpoints<\/a>.<\/p>\n

But, there are few features I’d love to have that aren’t there. They’re easy enough to add, but they’re really personal to me. Fortunately, I can add them myself.<\/p>\n

What is a custom tool?<\/h1>\n

The Custom Tool<\/i> feature in PowerShell Studio and PrimalScript lets you define commands in an INF file and add them to a menu.<\/p>\n

For example, I have huge Scripts library on One Drive where I keep all of my scripts. When I get to a certain point in my script development, I want to copy the current script to my Scripts library without closing it or finding its path.<\/p>\n

No problem! In PowerShell Studio, I click Tools<\/b> and, in the File group, click Custom Tool<\/b>, Copy to One Drive<\/b>.<\/p>\n

\"clip_image002\"<\/a><\/p>\n

In PrimalScript, I click Home<\/b> and, in the Build and Run group, click Custom Tool<\/b>, Copy to One Drive<\/b>.<\/p>\n

\"clip_image004\"<\/a><\/p>\n

As you can see, I also have options to copy to a different location, run a PowerShell Get-Acl cmdlet, run a script, open a module directory, open a Git shell, and open some very special INF files.<\/p>\n

Which commands can I use in a custom tool?<\/h1>\n

You can run almost any command, including cmd.exe commands, Windows PowerShell commands and scripts, and commands to executable files, like robocopy.exe, netstat.exe, and git.exe.<\/p>\n