I wish we just had c# in a script form instead of powershell
There is this: http://scriptcs.net/
Re:The .NET Language Strategy
by smoothdeveloper on Thursday February 02, 2017 @02:23PM
(#13553619)
Try fsharp with interactive, with paket it is also very easy to depend on complex graph of nuget dependencies.
You can, just need to have VS 2015 installed and use .csx files.
Re:The .NET Language Strategy
by nathanaldensr on Thursday February 02, 2017 @12:15AM
(#13548296)
Unfortunately, PowerShell lacks support for asynchronous programming. This has been a huge deal for me when trying to interface with newer .NET I/O-related assemblies, some of which only expose their methods as async.
At that point I abandoned powershell and just compiled a .NET exe
PowerShell is the recommended shell language. But I don't think it is considered a first-class .net language because Visual Studio does not have built-in support for it.
I thought it was on deck to take over default Windows shell/scripting status from hellish Batch