Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 587 Vote(s) - 3.56 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Terminating a script in PowerShell

#11
I coincidentally found out that <code>Break <i><UnknownLabel></i></code> (e.g. simply <code>Break <b>Script</b></code>, *where the label `Script` doesn't exists*) appears to break out of the entire script (even from within a function) and keeps the host alive.
This way you could create a function that breaks the script from anywhere (e.g. a recursive loop) without knowing the current scope (and creating labels):

Function Quit($Text) {
Write-Host "Quiting because: " $Text
Break Script
}
Reply

#12
I thought up a neat little trick to do just that, when I wanted a function to exit a script without throwing an error, but not exit the console if the function was used from there. It involves the `$MyInvocation` automatic variable's `CommandOrigin` property.

```powershell
if ( $MyInvocation.CommandOrigin -eq 'Internal' ) { exit }
```

If the function is ran from the console, the CommandOrigin will be Runspace.
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through