Hacker News Reader

Comment by intrasight | Hacker News Reader

For C# developers, have a look at csi (C# Interpreter) as a potential cmd replacement. I've been using it extensively for a couple weeks and like it very much. Also, the same scripts can, with little modifications, be posted to Azure Functions to run on the cloud.

View on HN

Wow, that is pretty awesome. Is there anyway to get Intellisense into the command window for CSI? I, all of a sudden, realized that I don't remember properties of the objects without it.

You can get that in VS via the Interactive Window (View->Other Windows->C# Interactive).

Theoretically you could implement a completion system for the terminal but we reused the WPF editor layers for the completion system rather than building a new one from scratch, so it isn't available in the terminal.

Also, all that is open source at https://github.com/dotnet/roslyn and the scripting core can be rehosted as an API.

See

https://msdn.microsoft.com/en-us/magazine/mt614271.aspx

and

http://www.hanselman.com/blog/InteractiveCodingWithCAndFREPL...

Last time I tried this there was no way to load nuget references. Very limited usability if that's true.

I wasn't trying to use it as a shell replacement but like a REPL for interactive development/prototyping. F# works better for this IIRC but I have not used F# several years - need to brush up on it.

You might want to look at ScriptCS for that, that also has a REPL and it does support Nuget packages.

When I work locally, I have a dummy VS project for grabbing assemblies from Nuget. With Azure Fuctions, your function.json file can reference nuget packages.

Or even better, the F# version of it (.fsx).

Reply on news.ycombinator.com