Add a #n directive to fsi which loads nuget packages about fsharp HOT 5 CLOSED

As @latkin has labelled, I think this is still a discussion/feature-request item. I'm not sure what @latkin and @KevinRansom want, but I personally think it is best to keep feature-requests off GitHub until a later stage (e.g. they are "approved" or a concrete design is available or an implementation pull request is available). Equally, I may be wrong, especially if good labelling is used. Ultimately it's up to the @latkin and @KevinRansom as current masters of the repo :)

from fsharp.

Relevant ticket: #1177

If this get implemented, as @dsyme described in a comment it would better be based on custom handlers and some type of URI scheme so it can be extended.

from fsharp.

It's possibile to add to fsi as cli parameter the name/assembly of a resolver? Using an external assembly resolver, there is no need to add special use case inside fsi (paket, nuget, etc).
Or as internal fsi command #resolver "path/to/resolver.dll
So #r "suave" is resolved by custom resolver, who can for example download the nuget package or use it from paket.

from fsharp.

@enricosada yes with @dsyme idea we won't have special case for nuget, paket etc.

His idea:

#r "references:nuget-handler.dll"  // specially attributed DLL
#r "SomeNugetPackage"

But we can refine.

What your propose about command line argument is an important point and I agree having possibility to reference the handler from there, and maybe also having fsi scan a folder with additional handlers would be great!

from fsharp.

Closing as suggestion is tracked by fsharp/fslang-suggestions#542

from fsharp.