Specify location of DLLs for C# Interactive
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No file or test is named. Start by locating C# Interactive's handling of #r and #help, then compare it with F# Interactive's #I behavior. Done means determining whether an equivalent DLL search-path mechanism exists and, if not, defining and documenting the requested behavior.
Written by the indexing model from the issue text.
Description
F# Interactive #help shows these options:
#r "file.dll";; Reference (dynamically load) the given DLL
#I "path";; Add the given search path for referenced DLLs
#load "file.fs" ...;; Load the given file(s) as if compiled and referenced
#time ["on"|"off"];; Toggle timing on/off
#help;; Display help
#quit;; Exit
F# Interactive command line options:
See 'fsi --help' for options
C# Interactive #help shows these options:
Keyboard shortcuts:
Enter If the current submission appears to be complete, evaluate it. Otherwise, insert a new line.
Escape Clear the current submission.
UpArrow Replace the current submission with a previous submission.
DownArrow Replace the current submission with a subsequent submission (after having previously navigated backwards).
Ctrl-C Exit the REPL.
REPL commands:
#help Display help on available commands and key bindings.
Script directives:
#r Add a metadata reference to specified assembly and all its dependencies, e.g. #r "myLib.dll".
#load Load specified script file and execute it, e.g. #load "myScript.csx".
One of the great features of F# scripts is the #I directive, which tells F# Interactive where to look for referenced DLLs.
Is there an equivalent way to do this in C# scripts?
- Dominant language
- C#
- Stars
- 78
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/interactive-window
-
dotnet/interactive-window#255 · 2 comments · 6 reactions · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/interactive-window#241 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
dotnet/interactive-window#230 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#185 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#184 ·
All issues in dotnet/interactive-window
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·