Monday, July 8, 2013

I'm using PowerShell more and more as an efficient MES Engineering tool recently and find it very convenient compared to writing codes in C# or VB Scripts. I've started to believe that PowerShell should go to our standard MES Engineer technical interview questions.
Ease of work with XML files, SQL Databases and Excel spreadsheets along with ability to write C# codes whenever required is increasing efficiency in MES mass configuration tasks.
Also the fact that windows have PowerShell pre-installed means I won't need to compile .exe and copy across to my server which is sometimes time-wasting with all security policies in place.
In slow Remote Desktop connections, the "less ceremony, more necessity" approach of PowerShell reveals it's value
I've already started collecting my personal arsenal of PowerShell cmdlets in Evernote and have Evernote on mobile devices and tablets installed. Shortness of PowerShell scripts means re-typing them won't be too much in case I can't copy&paste (e.g. having clipboard disabled on Citrix environments or being on a customer laptop not connected to any network or simply messed up clip-board in nested RDP sessions)




Homepage
Homepage