VSTS Hosted VS2017 Agent can't find fsi.exe about vsts-fsharp

[isaacabraham]

Can you test with the latest release?

[ScottHutchinson]

I'm having the same issue after reinstalling Windows 10 on my developer PC. It was working before the reinstall, but now fsi.exe is in a different location. What's the best way to run F# scripts?

This is my batch .cmd file:

:: Create a temporary drive letter mapped to your UNC root location
:: and effectively CD to that location
pushd %~dp0
"C:\Program Files (x86)\Microsoft SDKs\F#\4.0\Framework\v4.0\Fsi.exe" PostRelease.fsx
pause
:: Remove the temporary drive letter and return to your original location
popd

[ScottHutchinson]

I replaced the folder path with C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\CommonExtensions\Microsoft\FSharp and that fixed it. Is there some solution that does not assume nobody will move the fsi.exe file again? Please just stop moving my cheese! :O)

[isaacabraham]

Yeah, it's kind of whack-a-mole. To be honest I'm not sure what the best solution is really - I was trying to call FSI from within a Fake script last week and found it tough going within devops.