1

Closed

Write-Log -Message parameter backwards incompatible

description

I noticed today in re-using an older package's Deploy-Application.ps1 with the newer framework versions, that the -Message parameter of the Write-Log function used to be called -Text

So an 'old' function call of Write-Log -Text "Some Text" should now be Write-Log -Message "Some text", and the first variation now causes the script to fail.

While personally I absolutely prefer -Message as a parameter name, changing this might cause issues with backwards compatibility. Would it perhaps be possible to provide a "dummy" -Text variable which value gets put into $Message if present in the function call?
Closed Apr 14, 2015 at 1:01 PM by mmashwani
We have moved to a new homepage! You can now find us as http://psappdeploytoolkit.com.

This issue has been fixed in the latest 3.6.2 produciton release on our new repository on GitHub.
https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/releases

comments

mmashwani wrote Apr 3, 2015 at 8:22 AM

You can add an alias for the Message parameter like so:
[Parameter(Mandatory=$true,Position=0,ValueFromPipeline=$true,ValueFromPipelineByPropertyName=$true)]
[AllowEmptyCollection()]
[Alias('Text')]
[string[]]$Message,
I'll add the fix for backwards compatibility into the next release of the toolkit.