4 ms·
The big impediment imho between c# and scripting language is the whole Visual Studio project experience. With Roslyn they introduced the csx format for c# scri
by Pxtl 10y ago
The big impediment imho between c# and scripting language is the whole Visual Studio project experience. With Roslyn they introduced the csx format for c# scripts so you can have a stand-alone 1-file executable c# script, but the tooling hasn't caught up yet.
I'm using LinqPad for all kinds of one-off scripting jobs and loving it. I was trying to learn PowerShell for that task but I've finally given up on that. PowerShell has some great features, but the overall chaotic syntax just kills me.
- macca321 10y agoI think MS should buy LinqPad and give it away for free. It's just an amazing experience (having the full version is critical though).
- Pxtl 10y agoThere's a decent F/OSS implementation called CShell (bad name, I know, that's already a thing) http://cshell.net/ http://cshell.net/ Either way, neither of them run "true CSX files", but their own homegrown format that predates csx. But it has made me hopeful for the future of C# scripts.
- macca321 10y agoAnd another called RoslynPad
- sljd 10y agoThere can be some confusion between pipeline syntax and imperative syntax in Powershell, custom objects don't help either (i.e. `{...}` works differently than `[pscustomobject]{...}` for many cmdlets), but I'm curious what you consider chaotic enough to give up?
- RyanHamilton 10y agoFYI if any java developers are looking for a one file script running environment checkout http://jpad.io/ http://jpad.io/ I made it to scratch my own itch. It lets you run java snippets and view results as HTML even.
- svick 10y agoI think .Net Core is getting quite close to that. It still needs a project file, but it has a nice command line interface, which means you don't need VS. But I'll probably still keep using LinqPad anyway.