News for hackers. Stuff that matters.
Re:The .NET Language Strategy by frou_dh on Wednesday February 01, 2017 @04:16PM (#13545294)
Is PowerShell not considered a first-class .NET language?

I thought it was on deck to take over default Windows shell/scripting status from hellish Batch

Re:The .NET Language Strategy by simooooo on Wednesday February 01, 2017 @07:48PM (#13547031)
I wish we just had c# in a script form instead of powershell
Re:The .NET Language Strategy by nu5500 on Thursday February 02, 2017 @09:08AM (#13550538)
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.
Re:The .NET Language Strategy by pjmlp on Thursday February 02, 2017 @03:08PM (#13554130)
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.
Re:The .NET Language Strategy by simooooo on Thursday February 02, 2017 @10:39AM (#13551224)
At that point I abandoned powershell and just compiled a .NET exe
Re:The .NET Language Strategy by olavk on Wednesday February 01, 2017 @05:17PM (#13545938)
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.
Re:The .NET Language Strategy by pjmlp on Thursday February 02, 2017 @03:10PM (#13554145)
Yes, it does. You can even choose it during installation on VS 2015 and VS 17.

Still, there is the ISE as well, although not that feature rich.