![]() For example, you may use a particular source control solution for Folder A and another for Folder B. In this example GIT is used, but any command line tool will work including the command line tools you create with PowerShell Studio’s script to exe packager.Īfter creating or altering the CustomMenu.inf, you will need to restart PowerShell Studio in order to see the new commands:Īnother useful feature of the custom menu is the ability to create localized commands for specific folders. You can add a global set of commands to the custom tool menu by creating an INF file in PowerShell Studio’s application data folder:Ĭ:\ProgramData\SAPIEN\PowerShell Studio \CustomMenu.inf The new feature enables you to integrate virtually any solution that provides a command line tool. The custom tool menu allows you to customize and execute command lines tools at the click of a button. Our solution to the problem is the custom tool menu: We’ve used this common factor to resolve the problem. One thing in common all the source controls solutions previously mentioned have is command line tools. ![]() ![]() The varying nature of these tools could potentially make the integration outdated fairly quickly. The difficulty of supporting all these various source control solutions is that they all have different APIs and change over time. Similar to PrimalScript, we received requests to add support for GIT, Mercurial, and Subversion in PowerShell Studio. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |