Author | Chrissy LeMaire (@cl), netnerds.net |
Availability | Windows, Linux, macOS |
Want to see the source code for this command? Check out Get-DbatoolsChangeLog on GitHub.
Want to see the Bill Of Health for this command? Check out Get-DbatoolsChangeLog.
Opens the link to our online change log
Opens the link to our online change log. To see the local changelog instead, use the Local parameter.
Get-DbatoolsChangeLog
[-Local]
[-EnableException]
[<CommonParameters>]
PS C:\> Get-DbatoolsChangeLog
Opens a browser to our online changelog
PS C:\> Get-DbatoolsChangeLog -Local
Returns the content from changelog.md
Return the local change log to the console
Alias | |
Required | False |
Pipeline | false |
Default Value | False |
By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.
Alias | |
Required | False |
Pipeline | false |
Default Value | False |