|
4 mēneši atpakaļ | |
---|---|---|
.. | ||
.testloop.sh.swp | 4 mēneši atpakaļ | |
COPYRIGHT | 1 gadu atpakaļ | |
FindDuplicateTestMethodsInSameFileName.ps1 | 4 mēneši atpakaļ | |
FindDuplicateTests.ps1 | 4 mēneši atpakaļ | |
README.md | 1 gadu atpakaļ | |
Release.ps1 | 5 mēneši atpakaļ | |
Terminal.Gui.PowerShell.Build.psd1 | 1 gadu atpakaļ | |
Terminal.Gui.PowerShell.Build.psm1 | 1 gadu atpakaļ | |
Terminal.Gui.PowerShell.Core.psd1 | 1 gadu atpakaļ | |
Terminal.Gui.PowerShell.Core.psm1 | 1 gadu atpakaļ | |
Terminal.Gui.PowerShell.Git.psd1 | 1 gadu atpakaļ | |
Terminal.Gui.PowerShell.Git.psm1 | 1 gadu atpakaļ | |
Terminal.Gui.PowerShell.psd1 | 1 gadu atpakaļ | |
delist-nuget.ps1 | 4 mēneši atpakaļ | |
testloop.sh | 4 mēneši atpakaļ |
This directory contains PowerShell modules for use when working with Terminal.sln
These modules will be modifed and extended as time goes on, whenever someone decides to add something to make life easier.
These modules are designed for PowerShell Core, version 7.4 or higher, on any platform, and must be run directly within a pwsh process.\
If you want to use them from within another application, such as PowerShell hosted inside VSCode, you must first run pwsh
in that terminal.
As the primary development environment for Terminal.Gui is Visual Studio 2022+, some functionality may be limited, unavailable, or not work on platforms other than Windows.\ Most should still work on Linux, however.\ Functions which are platform-specific will be documented as such in their Get-Help documentation.
Specific requirements for each module can be found in the module manifests and will be automatically imported or, if unavailable, PowerShell will tell you what's missing.
From a PowerShell 7.4 or higher prompt, navigate to your Terminal.Gui repository directory, and then into the Scripts directory (the same directory as this document).
Run the following command to import all Terminal.Gui.PowerShell.* modules:
Import-Module ./Terminal.Gui.PowerShell.psd1
If the environment meets the requirements, the modules will now be loaded into the current powershell session and exported commands will be immediately available for use.
All exported functions and commandlets are provided with full PowerShell help annotations compatible with Get-Help
.
See The Get-Help documentation at Microsoft Learn for Get-Help information.
No environment changes made by the modules on import are persistent.
When you are finished using the modules, you can optionally unload the modules, which will also reset the configuration changes made on import, by simply exiting the PowerShell session (exit
) or by running the following command:\
NOTE DIFFERENT TEXT FROM IMPORT COMMAND!
Remove-Module Terminal.Gui.PowerShell
MIT License
Original Author: Brandon Thetford (@dodexahedron)
See COPYRIGHT in this directory for license text.