Open TheAngryByrd opened 6 years ago
i can repro in FSAC
I encountered this, too, when editing a FAKE script referencing Http.fs.
The workaround was to edit the file ./.fake/build.fsx/intellisense_lazy.fsx
manually and move the line
#r "../../packages/fakebuild/Http.fs/lib/net471/HttpFs.dll"
after the line
#r "../../packages/fakebuild/Hopac/lib/net471/Hopac.dll"
This is an old problem, but still relevant. I encountered this problem also in other generated references tools. Recently I ran into this using canopy. Canopy relies on Selenium.WebDriver, so this should be the correct order in the generated group.fsx:
#r "../../../../packages/uitests/Selenium.WebDriver/lib/net45/WebDriver.dll"
#r "../../../../packages/uitests/canopy/lib/netstandard2.0/canopy.dll"
Suppose, this issue is bigger than Paket.
Description
I have a build dependency group as such
When paket generates the
build.group.fsx
it givesHowever HttpFs is dependent on Hopac as seen in the Http.fs.fsx script:
So when trying to use it in a FAKE script
I end up with the error:
Repro steps
https://github.com/TheAngryByrd/paket-generate-out-of-order/
Expected behavior
Either generates the dependency order correctly or delegates to calling load on direct dependencies
Actual behavior
Generates correct dependency order
Known workarounds
Calling load on things within the group directly such as: