Skip to content

Releases: claudiospizzi/ScriptLogger

ScriptLogger v3.4.0

14 Jan 15:40

Choose a tag to compare

Release Notes:

  • Added: Feature to override the default streams like Write-Verbose to use the build-in functions to log messages (Start-ScriptLogger)
  • Added: Support for platform specific system log on Linux using the logger command (Write-ScriptLoggerPlatformLog)
  • Added: Option to include the PowerShell script stack trace in the error log message (Write-ErrorLog)
  • Added: Add the caller context information with script or function name and the line number to the log messages (Start-ScriptLogger)

ScriptLogger v3.3.0

05 Nov 17:44

Choose a tag to compare

Release Notes:

  • Added: The parent folder will be created, if it does not exists

ScriptLogger v3.2.0

29 Aug 14:43

Choose a tag to compare

Release Notes:

  • Added: The Path parameter for Start-ScriptLogger can now be an empty string

ScriptLogger v3.1.0

18 Feb 12:11

Choose a tag to compare

Release Notes:

  • Added: Optional log rotation (hourly, daily, monthly, yearly)

ScriptLogger v3.0.1

14 Feb 15:04

Choose a tag to compare

Release Notes:

  • Changed: Format of the script logger object to show the logger name

ScriptLogger v3.0.0

14 Feb 14:43

Choose a tag to compare

Release Notes:

  • Added: Support multiple messages for log functions
  • Changed: Support multiple loggers distinguished by a logger name
  • Changed: Default log file is now next to the executed script

ScriptLogger v2.0.0

10 Dec 15:27

Choose a tag to compare

Version 2.0.0

ScriptLogger v1.2.0

09 Mar 23:14

Choose a tag to compare

  • Add encoding option for the log file output
  • Add error handling for log file and event log output
  • Change console output from cmdlets to $Host.UI methods
  • Fix error record handling to log correct invocation information

ScriptLogger v1.1.1

09 Feb 16:44

Choose a tag to compare

  • Add formats and types resources
  • Fix tests for PowerShell 3.0 & 4.0

ScriptLogger v1.1.0

04 Feb 14:19

Choose a tag to compare

  • Add an ErrorRecord parameter to Write-ErrorLog
  • Return logger object inside Start-ScriptLogger