You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Paket.Restore.targets file currently on the master branch, I noticed the following line:
<PaketExePathCondition=" '$(PaketExePath)' == '' AND '$(OS)' == 'Windows_NT' AND Exists('$(PaketBootStrapperExeDir)') ">$(_PaketBootStrapperExeDir)paket.exe</PaketExePath>
Note the underscore in _PaketBootStrapperExeDir. The rest of the file defines this property as PaketBootStrapperExeDir with no underscore. I believe the underscore is a mistake that might cause the paket.exe file downloaded by the bootstrapper to not be found in the rest of Paket.Restore.targets, since MSBuild will treat $(PropertyNameThatDoesntExist) as the empty string and so the path would be paket.exe rather than .paket\paket.exe (assuming the bootstrapper is located in .paket).
I'll submit a PR to fix this typo.
The text was updated successfully, but these errors were encountered:
Description
In the
Paket.Restore.targets
file currently on the master branch, I noticed the following line:Note the underscore in
_PaketBootStrapperExeDir
. The rest of the file defines this property asPaketBootStrapperExeDir
with no underscore. I believe the underscore is a mistake that might cause thepaket.exe
file downloaded by the bootstrapper to not be found in the rest ofPaket.Restore.targets
, since MSBuild will treat$(PropertyNameThatDoesntExist)
as the empty string and so the path would bepaket.exe
rather than.paket\paket.exe
(assuming the bootstrapper is located in.paket
).I'll submit a PR to fix this typo.
The text was updated successfully, but these errors were encountered: