Scripting story, how to reference assemblies in script files

I use .fsx and .csx files to do scripting, nowadays I’m relying on paket to list and download my dependencies (transitive dependencies included), which has a side effect of those assemblies to land under packages/packagename/../ folder which I can then easily reference:

#r @"../../packages/packagename/lib/netcore/packagename.dll"

// I can now easily use the package

What is the story with dotnet cli for this?

[forki]

Scripting has always been one of the most important features in F# land and the rise of things like ScriptCs shows that it’s also important in C#. TBH I can’t really understand how fsx/csx files are not supported from day 1. We asked for this on every occasion.

@smoothdeveloper regarding dependencies. It looks like NuGet will never get the concept of solution-wide dependencies. But fortunately the new MSBuild-based project format allows Paket to hook in again and we have https://twitter.com/sforkmann/status/790856841106493441 - so that’s good.

I think paket’s “load scripts” will be the way to go for including deps in fsx. But it’s a long way.

[livarcocc]

This is something that is/should be worked out by the teams who own these scripting experiences, which is not the CLI. Closing this issue.