WIP: Generate an FSI 'context' for a project or file

[baronfel]

This is the start of some FSI-enhancement features I'd like to add to FSAC.

The gist is that I'd like to be able to spin up an FSI instance with all of the dependencies of a project pre-referenced, all project-file DEFINEs included, etc.

I'd also like to be able to spin up an FSI instance at a given point in a file in a project and have all of the same stuff loaded PLUS all of the files in the project up to the file/location the user specified.

This would give a nice drop-in experience to using FSI that is similar to the stack ghci command or starting the scala repl with the -classpath option set to the output of your build dir.

Tasks:

• implement project context
• implement file context
• test both in ionide
• answer open questions around project references
• answer open questions around handling multiple target frameworks

I want to get to something ~80%ish so that I can start using it and getting feedback.

[enricosada]

love it!

[baronfel]

With the release of dotnet-fsi and FSI previews having package manager support, it might make more sense to structure this as a load plug-in similar to #r project:path/to/project. That'd make this a bit more testable (the component would be a standalone tool that could be consumed in many ways) and it would make the ionide implementation simpler (ionide would just add an implicit #r to the project in question when the 'launch for project' option was chosen.

[baronfel]

this isn't the way to go with this work. The way forward is a #r project handler that can be loaded into both FSAC and dotnet-fsi contexts, so I'm going to close this.