the error was:
exception while resolving dependencies: System.Exception: Paket was not found in 'd:\dev\fsharp\sandbox\mlnet' or a parent directory, or 'C:\Users\Sorin'. Please download the tool and place it in one of the locations.
We need to make the tool search the default tools folder
#r "paket: nuget FParsec" open FParsec
dotnet fsiand Visual Studio 2019 copying the dll and having a version of paket under ~/.paket/paket.exe
dotnet paketin the future, by the time we made the prototype of the extension, I don't know if it was already used as a dotnet tool.
yes that sounds reasonable, I'm not sure it is doable to test if
dotnet paket exists because then it would incur the cost of running the command and checking the return value or parsing the output, not sure if that amounts for significant time before checking the folders.
There is also the question of the priority order in which those checks would go.
dotnet toolingwas not yet available as it is since dotnet core 3
and yes, no problem you don't have to look at implementing in the project, you may play around in script to try to call
dotnet paket or check the manifest.
dotnet tool list would give easy output to parse, looking if the implementation of that command can be referenced in the code.
~/.dotnet/tools/paket.exewould be for the global install.
Hello Paket folk! I'm moving from OCaml to F#, and I use Paket for managing dependencies--very much enjoying its power and flexibility, reminds me a bit of poetry for python. I'm finding that some libraries are hard to learn without having the source code available. I can manually hunt down the exact commit version I have on GitHub.
Is there a way for Paket to download the source code for a given dependency, and present it to my IDE (I use Rider, I can figure that half out) in a manner suitable for browser and runtime debugging?
I'm OK with pulling from GitHub if necessary, and hunting down the proper tag/hash. Surely someone else wants to do this! Thanks!
@JustinWick Have you tried running
dotnet paket installafter the
dotnet paket addcommand? I vaguely recall that in some cases,
dotnet paket adddidn't do the "install" step for reasons I can't recall now (probably I was doing something wrong). I've also found that sometimes I need to reload the VS Code window and suddenly the "namespace or module not defined" errors go away, because the VS Code language server process had cached an old version of the project and so it didn't see the results of
paket adduntil I refreshed the VS Code window.
Sorry I forgot to thank you. Yeah, it turns out deleting the cache and reloading solved most of these problems. After burning about 12 hours trying to get VS Code to work for F# without constant reloading, I gave up, moved to Rider, and couldn't be much happier. Rider + PyCharm for me now. My emacs is starting to get lonely.
clitooldirective. When I do it, it downloads the package and saves it to my packages folder, but it doesn't seem to add the local tool to the project manifest or otherwise make it available for use, I seem to need to do all that stuff manually. I don't see anything in the source code that suggests it operates on the manifest, am I missing something or is that how intended? If so then what is its use vs. doing
dotnet tool restore?