The Interactive Window is an interactive environment that helps you quickly learn APIs, play with language features, and experiment with other .NET technologies by providing you with immediate feedback.
error CS1703: Multiple assemblies with equivalent identity have been imported: 'C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\126.96.36.199__b03f5f7f11d50a3a\System.Configuration.dll' and 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_188.8.131.52__b03f5f7f11d50a3a\System.Configuration.dll'. Remove one of the duplicate references.
Any ideas ?
Really cool sample !!!
Nice, but I think you should embed LinqPad in Visual Studio/VSCode.
why not use F# repl?
@Jason, what bits are you using? Let me know if you repro this on Update 1
Does it support lambda expression evaluation?
Kasey - really nice intro! Well presented.
I've been waiting for a decent REPL experience in .NET... so tired of creating ConsoleApplication634 to try something out.
I had a lot of excitement for the C# repl window, then I tried it and quickly lost interest. Partly because I currently use a tool like LinqPad and really like it, and also because I was expecting the C# Repl window to automatically load (or at least give a command to load) the current solution into scope with all the Classes and related Libraries ready to go.
It would have made exploring a code base a delight. Not to mention the fact that you could use the repl while you are actively developing to experiment your ideas and then copy and paste the ones that work back into your solution. This is my current workflow with Linqpad for Linq Queries. I thought the C# REPL would be the ultimate tool for this workflow
What does Interactive C# use to display results? It's much better than the default "ToString" implementation and I would imagine it is easy to create a debug viewer that uses it.
@Siderite: if you're curious, you can see the code in ObjectFormatter in the roslyn codebase. Carrying it over into the expression evaluators for the debugger is on our backlog. You can follow that work/discussion here (note the issues referenced at the bottom of the issue as well).