Prerequisites
PSAppDeployToolkit.Tools version
Latest
PSAppDeployToolkit version
4.1.7
Describe the bug
I think that you accidentally forgot to convert "Path" and "Arguments" for the Execute-ProcessAsUser conversion.
Message : A parameter cannot be found that matches parameter name 'Path'.
FullyQualifiedErrorId : NamedParameterNotFound,Start-ADTProcessAsUser
The function was converted from Execute-ProcessAsUser to Start-ADTProcessAsUser but Path and Parameters stayed the same.
Steps to reproduce
- Convert any psadt 3 package with Execute-ProcessAsUser -Path $Path -Parameters $params
- See that the function Execute-ProcessAsUser was successfully converted but -Path and Parameters weren't converted to -Filepath and -ArgumentList
Environment data
Prerequisites
PSAppDeployToolkit.Tools version
Latest
PSAppDeployToolkit version
4.1.7
Describe the bug
I think that you accidentally forgot to convert "Path" and "Arguments" for the Execute-ProcessAsUser conversion.
Message : A parameter cannot be found that matches parameter name 'Path'.
FullyQualifiedErrorId : NamedParameterNotFound,Start-ADTProcessAsUser
The function was converted from Execute-ProcessAsUser to Start-ADTProcessAsUser but Path and Parameters stayed the same.
Steps to reproduce
Environment data
-