The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Thats how they cut their pizza's. When the son would finish a pizza in its entirety the father would proudly proclaim. "I'm gladiate the whole thing." **note this may not be historically accurate, but since I didn't live back then, it might not be completely incorrect either.
I are a dinosaur and I, too, have avoided PowerShell.
Having said that, I do find myself using it.
Over time, I've seen scripting done in various tools: VBScript, PERL, etc... but PowerShell seems to be the emerging tool.
Last week, I had to find a method to get the amount of memory installed on a computer and store that value; I COULD have done it in VBScript with WMI, but PowerShell was available and not that difficult to use.
I Googles the various pieces: get the installed memory, how to store the value in the system I'm using... and put them together into a single entity... and it worked the first time I ran it.
All I know about powershell is that the Package manager console in VS uses it, and in Win7, I managed to completely break it when I had Update 5 installed. Win they upgraded us to Win10, the version of powershell installed with win10 (v5.n?) was evidently too new for vs2013, and we had to install powershell 2.0 to get the package manager console working.
That's all I want to know about powershell.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
Last Visit: 2-Jul-20 10:07 Last Update: 2-Jul-20 10:07