v0.3.2

Fixed

• New-BusinessTimeSpan threw an exception in some scenarios for Windows PowerShell - see issue #1

v0.3.0

Changed

• Renamed Get-ElapsedBusinessTime to New-BusinessTimeSpan, and changed parameters -StartDate and -EndDate to -Start and -End, similar to New-TimeSpan and its datetime parameters.

v0.2.2

Fixed

• CmdletBinding attribute was in incorrect position for Add-WorkingDays. This caused PlatyPS to not generate docs properly. This fix does not provide any functional improvement to Add-WorkingDays. At this time, it is just necessary to push to source control which invokes the release pipeline.

v0.2.1

Fixed

• Get-ElapsedBusinessTime did not return correct result if -StartDate and -EndDate were on the same day, but it was a working day, and its time for both dates were outside of working hours

v0.2.0

Added

• New function Add-WorkingDays

v0.1.7

Changed

• Test-WorkingDay now has parameter validation to ensure -StartHour is less then -FinishHour
• Get-ElapsedBusinessTime now has parameter validation to ensure -StartHour is less then -FinishHour

v0.1.6

Fixed

• Get-ElapsedBusinessTime did not return correct result if -StartDate and -EndDate were on the same day, but it was a working day, and its time for both dates were outside of working hours

v0.1.5

Fixed

• Get-ElapsedBusinessTime did not return correct result if range between -StartHour and -FinishHour was not whole, ie was a span of time where minutes and seconds also needed consideration

v0.1.4

Fixed

• Get-ElapsedBusinessTime did not return correct result when either the start date or end date were outside of business hours
• Added line breaks in between each line for all comment based help

v0.1.2

Fixed

• Get-ElapsedBusinessTime did not return correct result where the number of working days between -StartDate and -EndDate was 1 but the date range spanned more than 1 calendar day, e.g. Sunday through to Monday.