Robocopy mode of Copy-File fails to copy files or folders when path begins with .\ or ..\

[DanGough]

Describe the bug
The Robocopy implementation in Copy-File does not like paths beginning with .\ or ..\
Having \..\ in middle of a folder path does work.

To Reproduce

These succeed but fail when -UseRobocopy is set to $true:

Copy-File -Path .\toolkit -Destination $env:temp -Recurse -UseRobocopy $false
Copy-File -Path .\TODO.txt -Destination $env:temp -Recurse -UseRobocopy $false
Copy-File -Path ..\PSAppDeployToolkit\TODO.txt -Destination $env:temp -Recurse -UseRobocopy $false
Copy-File -Path ..\PSAppDeployToolkit -Destination $env:temp -Recurse -UseRobocopy $false

Toolkit Version:
3.10.0 plus latest Copy-File fixes commited to Develop as of Apr 3, 2024.

[freedbygrace]

The following will fix seemingly fixes the issue.

$ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath("..\Testing")

Resolve path does the same thing, but throws an unnessary error if the path does not exist! Why, the world may never know.

In any case, the above worked in my use case, however, not sure if it works going back to Powershell 2.0, Powershell 7 etc.

Reference Link: https://stackoverflow.com/questions/3038337/powershell-resolve-path-that-might-not-exist

[DanGough]

Thanks for the tip!