Method invocation failed because [System.IO.Path] does not contain a method named 'GetRelativePath'.

[glopesdev]

The following command can fail when running the Export-Images.ps1 script from local PowerShell (e.g. from a build.ps1 script):

docfx-tools/modules/Export-Image.ps1

Line 41 in d33401b

$svgPathRelative = [IO.Path]::GetRelativePath($documentationRoot, $svgPath)

Method invocation failed because [System.IO.Path] does not contain a method named 'GetRelativePath'.

It seems by default PowerShell may not be using .NET Core for whatever reason. The CI scripts can run everything correctly, but it is often useful and faster to be able to debug locally, so would be great to provide some configuration or FAQ explaining how to workaround this.

[banchan86]

I came across this too, and my workaround was to upgrade PowerShell to 7+ as the default version included in Windows (Windows PowerShell 5.1) does not support .NET Core commands https://learn.microsoft.com/en-us/powershell/scripting/whats-new/differences-from-windows-powershell?view=powershell-7.5. I can document that workaround in the docfx article update.

[glopesdev]

@banchan86 Indeed, the method GetRelativePath is only available on .NET Core and the migration guide confirms that only PowerShell 6.0 or above runs on .NET Core.

This means that this change to the script makes it incompatible with the default Windows PowerShell 5.1 (the version shipped by default with Windows), and therefore requires explicit installation of the latest PowerShell, e.g. via WinGet:

winget install --id Microsoft.PowerShell

Need to consider first whether the change is worth the extra pain in default deployment, but will leave the workaround here for now as I am dealing with other difficulties in local debugging of the docs pipeline.

[NeuroThom]

I just hit this too. Made a fork that changes the script to work out of the box for ucl-open. Not sure if documenting an upgrade is better / preferred solution? PR here if it's of interest. #31

[glopesdev]

@NeuroThom just reviewed. I would like to know in what cases you are needing to run this script in the context of ucl-open. I would rather we are not too quick to diverge as it can make edge cases harder to understand.