PowerShell
-
I don't understand PowerShell, principally because its something I've always actively avoided. Looks nasty, but you can do some clever stuff with it so it seems. Some of my peers have this skill. I'm wondering if I should get to know it. Anybody here got any opinions good or bad?
Regards, Rob Philpott.
I would say it's definitely worth learning. If you work with Continuous Delivery using Microsoft's tools then Powershell becomes very useful. We us it in this scenario often to execute scripts remotely on our servers for backups and various other functions.
-
I don't understand PowerShell, principally because its something I've always actively avoided. Looks nasty, but you can do some clever stuff with it so it seems. Some of my peers have this skill. I'm wondering if I should get to know it. Anybody here got any opinions good or bad?
Regards, Rob Philpott.
One thing to keep in mind is that they keep all their modules in GitHub, and they like to introduce breaking changes in major release versions. I once upgraded the Azure PS module on a build server and it broke VSTS because they decided to stop supporting a parameter VSTS used extensively in its infrastructure.
-
I don't understand PowerShell, principally because its something I've always actively avoided. Looks nasty, but you can do some clever stuff with it so it seems. Some of my peers have this skill. I'm wondering if I should get to know it. Anybody here got any opinions good or bad?
Regards, Rob Philpott.
-
I don't understand PowerShell, principally because its something I've always actively avoided. Looks nasty, but you can do some clever stuff with it so it seems. Some of my peers have this skill. I'm wondering if I should get to know it. Anybody here got any opinions good or bad?
Regards, Rob Philpott.
PowerShell is awesome. Simply amazing. Easy to learn. Get a copy of Windows Powershell Programming for Absolute Beginners. You will learn it easily, and never look back at that ugly CMD Prompt again.
-
I don't understand PowerShell, principally because its something I've always actively avoided. Looks nasty, but you can do some clever stuff with it so it seems. Some of my peers have this skill. I'm wondering if I should get to know it. Anybody here got any opinions good or bad?
Regards, Rob Philpott.
I have been a linux user since the late 90s. Whenever my arm was twisted to work on on a windows setting (all to often X| ) the first thing I always did was install cygwin on it before anything else. bash saved me from early insanity. I never looked at PowerShell, maybe I have missed something. Next time I'm young I'll try it, promise.
-
I have been a linux user since the late 90s. Whenever my arm was twisted to work on on a windows setting (all to often X| ) the first thing I always did was install cygwin on it before anything else. bash saved me from early insanity. I never looked at PowerShell, maybe I have missed something. Next time I'm young I'll try it, promise.
Is there really anything else ever needed if you have bash, awk, sed and grep?
-
Is there really anything else ever needed if you have bash, awk, sed and grep?
For miniscripts no, those will usually be sufficient. if not then python, perl, tcl... whatever.
-
I don't understand PowerShell, principally because its something I've always actively avoided. Looks nasty, but you can do some clever stuff with it so it seems. Some of my peers have this skill. I'm wondering if I should get to know it. Anybody here got any opinions good or bad?
Regards, Rob Philpott.
PowerShell works great once you learn its syntax and quirks. I've only had a few commands that don't transfer over exactly from the command prompt to powershell and all you need to do is type "cmd" in PowerShell go get the normal command line so it's not that big a deal that it's now the default in Windows. I highly recommend watching at least the first video in the Microsoft Virtual Academy on PowerShell to get an idea of the basics. Microsoft PowerShell Tutorial & Training Course – Microsoft Virtual Academy[^]
-
This is not true. You may use try-catch-blocks and also multi-threading. We created some powerful scripts here already. I agree that C# is smarter for developers. But I must admit that pipelining in PS is a very strong and useful mechanism.
Also, it is possible to call C# from powershell.
-
I don't understand PowerShell, principally because its something I've always actively avoided. Looks nasty, but you can do some clever stuff with it so it seems. Some of my peers have this skill. I'm wondering if I should get to know it. Anybody here got any opinions good or bad?
Regards, Rob Philpott.
I used to find that I could do anything I wanted to do in Python, and more easily - but recently I've been working in a locked down environment without python, but with Powershell, so I've forced myself to learn. I initially found it odd to work with - but it is making more sense over time. Syntactically there are still some things I find quirky compared to for example Unix shell scripting. I'm a whiz at batch files . . . but now I'm finding that I use batch less than Powershell. . . so it must be growing on me. . . . and it does seem to be the future for Microsoft.